Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: ETA on git conversion
Date: Wed, 08 Oct 2008 12:17:08 +0200	[thread overview]
Message-ID: <gci1b5$d57$1@ger.gmane.org> (raw)
In-Reply-To: <200810081210.00494.openembedded@haerwu.biz>

On 08-10-2008 12:10, Marcin Juszkiewicz wrote:
> Wednesday 08 of October 2008 07:51:15 Holger Freyther napisał(a):
>
>> we would like to switch to git by next wednesday. Jan Lübbe went
>> through the hassle to fix two issues in my mtn2git.py and we are
>> happy with the metadata and can even unite it with the data exported
>> from bitkeeper.
>
>> The plans would be:
>> 	- Send your public ssh keys if you have not done so
>
> Send them to who? Mickeyl, Koen, Holger, Richard or someone other?

As was said only 7 days ago, on this very list:

http://lists.linuxtogo.org/pipermail/openembedded-devel/2008-October/006291.html

We have received a grand total of 14 git keys since then.

regards,

Koen

>
>> Tuesday:
>> 	- Set monotone readonly 16h german time
>> 	- merge the multiple heads (if they exist)
>> 	- Try to add the revs from now to tuesday to git
>
>> Wednesday:
>> 	- Be back up with git and use that as primary system.
>> 	- Disable monotone completely
>
> I would suggest leaving monotone read-only for two weeks so people will
> have a time to switch. Also adding file like README-THIS-IS-NOT-UPDATED-
> SINCE-WE-SWITCHED-TO-GIT with some info would be nice.
>
>> Thanks to Jan for wrestling with monotone, git, the script and the
>> data and we will keep you informed about how the migration is going.
>
> Thanks to all people envolved into this switch. My contributions to OE
> were smaller last time due to my work on Poky but now, when we will be
> using git I plan to merge some interesting stuff to the OE (my monotone
> knowledge is smaller then it was year ago).
>





  reply	other threads:[~2008-10-08 10:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08  5:51 ETA on git conversion Holger Freyther
2008-10-08  7:10 ` Khem Raj
2008-10-08  7:31   ` Tom Rini
2008-10-08  8:07 ` Koen Kooi
2008-10-08 10:52   ` Philip Balister
2008-10-08 10:56     ` Michael Krelin
2008-10-08 11:03   ` Holger Freyther
2008-10-08 11:18     ` Koen Kooi
2008-10-08 13:19       ` Leon Woestenberg
2008-10-08 13:32         ` Philip Balister
2008-10-08 15:57       ` Holger Freyther
2008-10-08 16:51         ` Michael Krelin
2008-10-08 16:54         ` Koen Kooi
2008-10-08 18:05         ` Philip Balister
2008-10-08 23:47         ` Rod Whitby
2008-10-09  9:39           ` git and branches Sledz, Steffen
2008-10-09 20:37             ` Denys Dmytriyenko
2008-10-09 22:31             ` Rod Whitby
2008-10-14 14:41           ` ETA on git conversion Jonas Bonn
2008-10-08 10:10 ` Marcin Juszkiewicz
2008-10-08 10:17   ` Koen Kooi [this message]
2008-10-08 13:06 ` Otavio Salvador
2008-10-14 14:12 ` Holger Freyther
2008-10-14 21:41 ` Holger Freyther
2008-10-15  0:29   ` Rodrigo Vivi
2008-10-15  2:17   ` Rod Whitby
2008-10-15  2:30     ` Rod Whitby
2008-10-15  9:31   ` Uli Luckas
2008-10-15 14:14   ` Mark Brown

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='gci1b5$d57$1@ger.gmane.org' \
    --to=k.kooi@student.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox