git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Kelly F. Hickel" <kfh@mqsoftware.com>
To: "Junio C Hamano" <gitster@pobox.com>,
	"Johannes Sixt" <j.sixt@viscovery.net>
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:31:51 -0500	[thread overview]
Message-ID: <63BEA5E623E09F4D92233FB12A9F794302E0F9D9@emailmn.mqsoftware.com> (raw)
In-Reply-To: <7v3adhj2ku.fsf@gitster.siamese.dyndns.org>

> -----Original Message-----
> From: Junio C Hamano [mailto:gitster@pobox.com]
> Sent: Friday, March 13, 2009 2:37 AM
> To: Johannes Sixt
> Cc: Kelly F. Hickel; git@vger.kernel.org
> Subject: Re: newb: Given a commit id, find which branches have it as
an
> ancestor
> 
> Johannes Sixt <j.sixt@viscovery.net> writes:
> 
> > 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.
> 
> It could be that there are more commits that are built on top of the
> one
> you are aware of.  Finding unreachable commits from "git fsck --full"
> might help you find them.

Thanks, turned out to be my misunderstanding of how to do incremental
imports
(see my response to Johannes).

Thanks for the help,
-Kelly

  reply	other threads:[~2009-03-13 13:33 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
2009-03-13  7:37     ` Junio C Hamano
2009-03-13 13:31       ` Kelly F. Hickel [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=63BEA5E623E09F4D92233FB12A9F794302E0F9D9@emailmn.mqsoftware.com \
    --to=kfh@mqsoftware.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j.sixt@viscovery.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).