Re: remotes/* for "foreign" archives

From: Seth Falcon <sethfalcon@gmail.com>
Date: Nov 21, 2006, 15:13 UTC
Message-ID: <m2y7q4bzo7.fsf@ziti.local>
In-Reply-To: <86r6vwkfti.fsf@blue.stonehenge.com>

merlyn@stonehenge.com (Randal L. Schwartz) writes:

Show 15 quoted lines

> It occurred to me after posting this, and while still thinking about the
> presentation I'm writing, that it'd be interesting if "get-fetch" could hide
> this from me.
>
> If the file in remotes/origin looked something like:
>
>         Pull: !git-svn multi-fetch trunk
>         Push: !git-svn commit
>
> then git-fetch and git-push could treat "origin" as a "foreign" branch
> and indirect through these commands.
>
> Then I could just use "git-pull" naively, and it would git-fetch origin,
> invoking git-svn multi-fetch trunk to update it, and later I could
> git-push and it would use git-svn commit.

This sort of integration could be quite cool. But I think the most common use of git-svn is with rebase and not pull. My experience with git-svn and pull is that I very quickly ended up making broken commits to svn --- I've had much better luck rebasing.