From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: please check BK&MTN to GIT conversion dry-run repository
Date: Thu, 16 Oct 2008 10:39:55 +0100 [thread overview]
Message-ID: <1224149995.1603.8.camel@ted> (raw)
In-Reply-To: <1224145911.31453.44.camel@localhost>
On Thu, 2008-10-16 at 10:31 +0200, Jan Lübbe wrote:
> Oh, this is new to me :/ When i talked about importing BK history with
> Holger he didn't seem to have any doubts.
I thought I'd made the idea of using a graft for this clear but
obviously not :(.
> >From what i just read about grafts, it will replace the parent
> information for the specified commit. So we could still replace the
> current BK import with the correct one.
>
> Grafts are local only though.
They won't get passed through a git clone? I guess that isn't a problem
as long as we do this on the master repository and document it.
> > > and
> > > still allows to find ot where the files come from. If someone figures
> > > out how to do a better conversion, we can still rebase, it that is
> > > desired.
> >
> > No, we don't want to ever rebase. I'd much prefer we had a graft for
> > that point in time so we can just replace the history as and when we
> > come up with a better version.
>
> We could import BK again (correctly) into a separate branch and then
> document how to graft it to instead of the current stuff.
It is now too late to rebuild the tree without the BKCVS information?
I'd prefer not to have the wrong information hanging around if at all
possible.
Cheers,
Richard
next prev parent reply other threads:[~2008-10-16 9:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 13:13 please check BK&MTN to GIT conversion dry-run repository Jan Luebbe
2008-10-14 13:17 ` Jan Luebbe
2008-10-14 14:23 ` Koen Kooi
2008-10-15 9:27 ` Richard Purdie
2008-10-15 13:42 ` Jan Lübbe
2008-10-15 15:20 ` Richard Purdie
2008-10-16 8:31 ` Jan Lübbe
2008-10-16 9:39 ` Richard Purdie [this message]
2008-10-17 15:10 ` Koen Kooi
2008-10-17 14:54 ` Michael 'Mickey' Lauer
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=1224149995.1603.8.camel@ted \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 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.