From: Chris Packham <judge.packham@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: GIT <git@vger.kernel.org>
Subject: Re: git fast-export/fast-import *facepalm*
Date: Thu, 27 May 2010 14:57:06 -0700 [thread overview]
Message-ID: <AANLkTik9QxiAjZHigx0YS5ybZwj6U7l0fK-byUmBirnO@mail.gmail.com> (raw)
In-Reply-To: <20100527210328.GN16470@spearce.org>
On Thu, May 27, 2010 at 2:03 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> Chris Packham <judge.packham@gmail.com> wrote:
>> What I've ended up with is a repository with a detached set of changes i.e
>>
>> o -o l - l - l - l - l - l o - master
>> \ /
>> o - o - o - o - o - o
>>
>> o = our commits
>> l = linux commits
>>
>> Because the code is common textually I think what I really should have done is
>>
>> (cd linux-2.6.32.y; git format-patch v2.6.32.12..v2.6.32.14) | git am
>>
>> Which I'll give a try in a minute. In the meantime is there anyway for
>> me to safely remove the upstream linux commits without loosing our
>> commits in the process?
>
> If I read your diagram right, the l-l-l chain isn't connected at
> all to your graph, so it should just get removed with `git gc`.
>
Well it _looks_ detached in gitk I can't see any merge commits. I've
tried git gc but no joy. Maybe I need to tell it to be a bit more
thorough.
> But if it is connected due to a merge with your master, lookup the
> merge and find its parent which is your local stuff and `git reset
> --hard` to that commit.
>
> --
> Shawn.
>
next prev parent reply other threads:[~2010-05-27 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 20:46 git fast-export/fast-import *facepalm* Chris Packham
2010-05-27 21:03 ` Shawn O. Pearce
2010-05-27 21:57 ` Chris Packham [this message]
2010-05-27 22:01 ` Avery Pennarun
[not found] ` <AANLkTin-SCsgxAUCCYILIHaq-sLDfCgTDfY_Kvc5UVSt@mail.gmail.com>
[not found] ` <AANLkTinJd1hZE6LiJRHWYknS7e2YUHtKApTaKfpPPfKJ@mail.gmail.com>
2010-05-27 22:18 ` Chris Packham
2010-05-27 22:57 ` Chris Packham
2010-05-27 23:03 ` Chris Packham
2010-05-27 21:19 ` Avery Pennarun
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=AANLkTik9QxiAjZHigx0YS5ybZwj6U7l0fK-byUmBirnO@mail.gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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).