From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>, git@vger.kernel.org
Subject: Re: [question] how can i verify whether a local branch is tracking a remote branch?
Date: Sun, 05 Apr 2009 22:28:02 -0700 [thread overview]
Message-ID: <7vy6uecpwd.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090406043426.GC12341@coredump.intra.peff.net> (Jeff King's message of "Mon, 6 Apr 2009 00:34:26 -0400")
Jeff King <peff@peff.net> writes:
> I don't think it would be unreasonable to expose this functionality via
> "for-each-ref". Something like this (which would need cleanup,
> documentation, and perhaps a :short variant):
I think that is a sane approach, but isn't "tracking" a misnomer? I think
what you are describing is what is called "the upstream branch" by the
description of Documentation/config.txt::branch.<name>.merge, and not what
people call "tracking branch" (see Documentation/glossary-content.txt).
In a repository with a handcrafted fetch refspec, being able to show
"tracking" information would also be interesting (e.g. a clone of git.git
made with pre-1.5.0 git would say "origin's master" for refs/heads/origin
and "origin's next" for refs/heads/next), but the separate-remote layout
is the default these days, so it wouldn't be so interesting anymore. In
other words, I am not suggesting you to add "tracking" information.
I also wonder if you want to say "this remote" and "that branch"
separately. As far as I can tell you are not giving the former but only
the latter information?
next prev parent reply other threads:[~2009-04-06 5:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 10:32 [question] how can i verify whether a local branch is tracking a remote branch? Paolo Ciarrocchi
2009-04-05 14:44 ` Jeff King
2009-04-05 21:25 ` Paolo Ciarrocchi
2009-04-06 4:34 ` Jeff King
2009-04-06 5:28 ` Junio C Hamano [this message]
2009-04-06 5:49 ` Jeff King
2009-04-06 8:30 ` Paolo Ciarrocchi
2009-04-06 21:25 ` Jeff King
2009-04-06 22:00 ` Paolo Ciarrocchi
2009-04-07 4:41 ` Jeff King
2009-04-06 12:00 ` Michael J Gruber
2009-04-06 21:29 ` Jeff King
2009-04-07 7:59 ` Michael J Gruber
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=7vy6uecpwd.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=peff@peff.net \
/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).