From: Pascal Obry <pascal@obry.net>
To: "Santi Béjar" <santi@agolina.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Finding the name of the parent branch?
Date: Fri, 30 Jan 2009 15:06:12 +0100 [thread overview]
Message-ID: <a2633edd0901300606ub4c507bocccb6747b436f01f@mail.gmail.com> (raw)
In-Reply-To: <adf1fd3d0901300557t19ca4bccn7fe24013a05d2d57@mail.gmail.com>
Santi,
Thanks for your patience!
> gitk topicbranch ^trackingbranch
>
> But I agree that a way to refer to the tracking branch would be great, as:
>
> branch^{origin}
>
> so you can say, for example:
>
> gitk topicbranch ^topicbranch^{origin}
That's exactly what I'm looking for!
> At least part of. You have to understand the branch model:
>
> git model:
> * a branch is just a pointer to a commit
> * you cannot say "this commit was done in that branch"
> * what you can say is "this commit is contained in that branch"
The second point wasn't clear to me.
I had 2 out of 3 OK :)
Thanks.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
next prev parent reply other threads:[~2009-01-30 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 10:56 Finding the name of the parent branch? Pascal Obry
2009-01-30 11:18 ` Santi Béjar
2009-01-30 12:56 ` Pascal Obry
2009-01-30 13:16 ` Santi Béjar
2009-01-30 13:35 ` Pascal Obry
2009-01-30 13:57 ` Santi Béjar
2009-01-30 14:06 ` Pascal Obry [this message]
2009-01-30 14:46 ` Santi Béjar
2009-01-30 13:35 ` Michael J Gruber
2009-01-30 14:26 ` Thomas Koch
2009-01-30 15:58 ` Pascal Obry
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=a2633edd0901300606ub4c507bocccb6747b436f01f@mail.gmail.com \
--to=pascal@obry.net \
--cc=git@vger.kernel.org \
--cc=santi@agolina.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).