From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: please check BK&MTN to GIT conversion dry-run repository
Date: Wed, 15 Oct 2008 10:27:59 +0100 [thread overview]
Message-ID: <1224062879.5189.49.camel@ted> (raw)
In-Reply-To: <1223990240.29816.58.camel@polaris>
On Tue, 2008-10-14 at 15:17 +0200, Jan Luebbe wrote:
> And here it is: http://git.sicherheitsschwankung.de/?p=jan/oetest.git
The BKCVS conversion still has the problems I wanted to get resolved
before we did this for example:
http://git.sicherheitsschwankung.de/?p=jan/oetest.git;a=commit;h=66944efa040bdf36062522c7c33413fc1e039d83
Where two commits have been rolled into one.
The original plan was to add the BKCVS later as a git tree graft rather
than hardcoding it into the history now in a broken form. Is it too late
to do this now?
Cheers,
Richard
next prev parent reply other threads:[~2008-10-15 9:33 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 [this message]
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
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=1224062879.5189.49.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox