From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Paul Gardiner" <osronline@glidos.net>, git@vger.kernel.org
Subject: Re: How to find where a branch was taken from.
Date: Fri, 21 Mar 2008 13:39:11 -0400 [thread overview]
Message-ID: <32541b130803211039h1f5b8da5k8fb353d46e57b05e@mail.gmail.com> (raw)
In-Reply-To: <7v4pb0qw28.fsf@gitster.siamese.dyndns.org>
On Fri, Mar 21, 2008 at 5:13 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Paul Gardiner <osronline@glidos.net> writes:
> > I need a command that will find the remote branch from which
> > the currently checked out branch was started. I don't know
> > git very well, and the only way I can think to do it so far
> > is to iterate over the remote branches and find the one
> > for which git-rev-list <branch>..HEAD gives the smallest
> > number of objects. I'm guessing there must be a better
> > way. Any ideas?
>
> There will be _no_ way. It is simply impossible.
>
> $ git checkout -b my-new-branch origin/somerandombranch~27^2^2~23
>
> is a perfectly valid way to create a new branch.
>
> You would probably want to re-think in a bigger picture, _why_
> you would want to find such information, [...]
I frequently want to do this. Basically, I start from "some version"
of the upstream program, and I put together some patches, then I want
to use rebase to reorder and recombine them before I send them in.
In order to do this, however, I'm forced to remember where I got my
"original" version from, which isn't even that important. As the
developer of a particular patch, all I *really* should have to know
is: a) here are the things I added since I made my topic branch, and
b) here is the branch I want to rebase them onto so I can submit my
cleaned patches upstream.
If git would explicitly track the rev at which my branch was created,
it would mostly solve *my* problem here, even though I wouldn't know
the *name* of the branch I branched from.
Alternatively, we could avoid tracking anything extra at all. If git
could suggest a branch or tag that mine is "currently closest to",
ie., the one that has as many of the commits from my branch as
possible (even if it has additional commits that I don't have), then
that might be the branch I'm interested in. If not, I could use this
comment repeatedly to produce a "chain of parent branches", one of
which is probably the one I'm interested in.
Have fun,
Avery
next prev parent reply other threads:[~2008-03-21 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 9:05 How to find where a branch was taken from Paul Gardiner
2008-03-21 9:13 ` Junio C Hamano
2008-03-21 9:15 ` Junio C Hamano
2008-03-21 17:39 ` Avery Pennarun [this message]
2008-03-21 18:32 ` Charles Bailey
2008-03-21 18:48 ` Avery Pennarun
2008-03-21 20:03 ` Dmitry Potapov
2008-03-21 20:22 ` Daniel Barkalow
2008-03-21 20:25 ` J. Bruce Fields
2008-03-22 12:12 ` Paul Gardiner
2008-03-22 16:41 ` Jeff King
2008-03-22 16:54 ` Paul Gardiner
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=32541b130803211039h1f5b8da5k8fb353d46e57b05e@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=osronline@glidos.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).