From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Old bitkeeper repository
Date: Mon, 31 Mar 2008 09:15:25 +0200 [thread overview]
Message-ID: <fsq32d$6ds$1@ger.gmane.org> (raw)
In-Reply-To: <1206919092.4838.23.camel@dax.rpnet.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Richard Purdie schreef:
| Hi,
|
| I've been experimenting with the bitkeeper cvs dump we have of the OE
| repository that was there. I'm planning on turning this into a git
| repository so we can more easily see what was in there.
I did that for hg a while ago: http://ewi546.ewi.utwente.nl:8000/
| If we did switch to git/hg/scm of the month, what commit ids would we
| want to be using?
I'd say we stick the the current ones and turn those into working email
addresses for everyone.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFH8I+NMkyGM64RGpERAi3QAJ9bQxDGO6o2Wutx5xD4UnYzBJUJVgCfXaap
wOunXG9pWE7mkK7RvPHDTkA=
=MoEP
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-03-31 7:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 23:18 Old bitkeeper repository Richard Purdie
2008-03-31 7:15 ` Koen Kooi [this message]
2008-10-08 10:18 ` Jan Luebbe
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='fsq32d$6ds$1@ger.gmane.org' \
--to=koen@dominion.kabel.utwente.nl \
--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.