From: Johannes Sixt <j.sixt@viscovery.net>
To: "Kelly F. Hickel" <kfh@mqsoftware.com>
Cc: git@vger.kernel.org
Subject: Re: newb: Given a commit id, find which branches have it as an ancestor
Date: Fri, 13 Mar 2009 08:14:45 +0100 [thread overview]
Message-ID: <49BA07E5.2080701@viscovery.net> (raw)
In-Reply-To: <63BEA5E623E09F4D92233FB12A9F794302E0F9BA@emailmn.mqsoftware.com>
Kelly F. Hickel schrieb:
>> From: git-owner@vger.kernel.org [mailto:git-owner@vger.kernel.org] On
>> Behalf Of Johannes Sixt
>> Sent: Thursday, March 12, 2009 10:38 AM
>> To: Kelly F. Hickel
>
>> $ git branch -a --contains the-sha1
>>
>> -- Hannes
>>
>
> Thanks, that looks like a really useful command.
>
> Unfortunately, in this case it didn't print anything out (neither did
> "git branch -r -a sha1").
>
> What I'm beginning to suspect is that all the commits that should have
> gone to master went to some unnamed branch.
> Is that reasonable/possible/likely? This commit has a full ancestry,
> but doesn't appear to be on any branch.
>
> In the above question there's an assumption that if a branch exists
> without a name, then git branch -a --contains wouldn't print anything
> out, is that correct?
Correct.
Your best bet is perhaps that you create a branch at the commit
$ git branch tmp-branch your_sha1
so that the commits are not lost, then you cherry-pick them to master.
-- Hannes
next prev parent reply other threads:[~2009-03-13 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <63BEA5E623E09F4D92233FB12A9F794302E0F9B2@emailmn.mqsoftware.com>
2009-03-12 19:38 ` newb: Given a commit id, find which branches have it as an ancestor Kelly F. Hickel
2009-03-13 7:14 ` Johannes Sixt [this message]
2009-03-13 7:37 ` Junio C Hamano
2009-03-13 13:31 ` Kelly F. Hickel
2009-03-13 13:30 ` Kelly F. Hickel
2009-03-13 16:20 John Dlugosz
-- strict thread matches above, loose matches on Subject: below --
2009-03-12 15:21 Kelly F. Hickel
2009-03-12 15:38 ` Johannes Sixt
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=49BA07E5.2080701@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=kfh@mqsoftware.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.