Re: setting up tracking on push

From: John Tapsell <johnflux@gmail.com>
Date: Mar 6, 2009, 03:17 UTC
Message-ID: <43d8ce650903051917r2919becckf13171c8e015b652@mail.gmail.com>
In-Reply-To: <buofxhr2vta.fsf@dhlpc061.dev.necel.com>

2009/3/6 Miles Bader <miles@gnu.org>:

Show 25 quoted lines

> [...sorry if this is a dup -- my previous attempt didn't seem to take...]
>
> Is there an "easy" way to set up tracking for a branch which starts out
> locally, and is eventually pushed to a remote?
>
> E.g., I create a new local branch "grognul", and then later propagate it
> to my remote site using:
>
>  git push origin grognul
>
> That works great (creating origin/grognul), but to set up tracking, I
> currently edit .git/config (not insanely difficult, but vaguely
> annoying).  This is as opposed to a branch which starts out remotely,
> and is pulled, where one can just use "git branch --track" or "git
> checkout --track" (or use a config option to do so by default).
>
> I vaguely feel like I should be able to do:
>
>  git push --track origin grognul
>
> [I do this particular action -- creating a branch locally and then
> pushing it to origin -- very very often, thus my desire for a handy
> option.]
>
> What do other people think?

I got bitten by this too, and there's no clue given how to set up the tracking. I'd like it to even ask the user when pushing:

$ git push origin grognul
Pushing blah blah...
 Do you want to track this? [Y/N/?]

:-)

John

Show 10 quoted lines

>
> -miles
>
> --
> Inhumanity, n. One of the signal and characteristic qualities of humanity.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>