From: John Tapsell <johnflux@gmail.com>
To: Miles Bader <miles@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: setting up tracking on push
Date: Fri, 6 Mar 2009 03:17:58 +0000 [thread overview]
Message-ID: <43d8ce650903051917r2919becckf13171c8e015b652@mail.gmail.com> (raw)
In-Reply-To: <buofxhr2vta.fsf@dhlpc061.dev.necel.com>
2009/3/6 Miles Bader <miles@gnu.org>:
> [...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
>
> -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
>
next prev parent reply other threads:[~2009-03-06 3:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 3:07 setting up tracking on push Miles Bader
2009-03-06 3:17 ` John Tapsell [this message]
2009-03-06 4:49 ` Jay Soffian
2009-03-06 10:45 ` Johannes Schindelin
2009-03-06 11:15 ` Miles Bader
2009-03-06 14:15 ` Jeremy O'Brien
2009-03-06 15:43 ` Jay Soffian
2009-03-06 16:29 ` Miles Bader
2009-03-10 20:26 ` Marc Branchaud
2009-03-10 23:09 ` Jeff King
2009-03-11 1:52 ` Jay Soffian
2009-03-11 2:04 ` Jeff King
2009-03-11 2:59 ` Jay Soffian
2009-03-11 3:06 ` Jeff King
2009-03-11 3:40 ` Jay Soffian
2009-03-11 3:44 ` Jay Soffian
2009-03-11 3:57 ` Jeff King
2009-03-11 4:15 ` Jay Soffian
2009-03-24 9:58 ` Jakub Narebski
2009-03-11 4:37 ` Junio C Hamano
2009-03-11 4:56 ` Miles Bader
2009-03-11 5:03 ` Miles Bader
2009-03-11 5:22 ` Jay Soffian
2009-03-11 21:39 ` Marc Branchaud
2009-03-11 6:32 ` Jeff King
2009-03-11 10:02 ` Nanako Shiraishi
2009-03-11 16:40 ` Jeff King
2009-03-12 0:08 ` John M. Dlugosz
2009-03-12 0:58 ` Jay Soffian
2009-03-12 1:11 ` Junio C Hamano
2009-03-12 1:16 ` Jay Soffian
2009-03-12 1:14 ` Jay Soffian
2009-03-12 1:21 ` Jay Soffian
2009-03-15 3:28 ` John M. Dlugosz
2009-03-15 12:36 ` Jay Soffian
2009-03-16 1:07 ` John M. Dlugosz
2009-03-16 1:43 ` Jay Soffian
2009-03-15 18:33 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43d8ce650903051917r2919becckf13171c8e015b652@mail.gmail.com \
--to=johnflux@gmail.com \
--cc=git@vger.kernel.org \
--cc=miles@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).