| 1 |
On Tue, Oct 2, 2012 at 5:21 PM, Rich Freeman <rich0@g.o> wrote: |
| 2 |
> On Tue, Oct 2, 2012 at 4:20 PM, Gregory M. Turner <gmt@×××××.us> wrote: |
| 3 |
>> Brian Harring wrote: |
| 4 |
>>> |
| 5 |
>>> replay it into git via tailor; |
| 6 |
>>> |
| 7 |
>> |
| 8 |
>> Never knew about that tool... not sure about the wisdom of adding an extra |
| 9 |
>> moving part just to keep the lights on for those few hours... Given the "2G |
| 10 |
>> of history" issue Diego mentioned, which if I understand correctly, |
| 11 |
>> effectively means that the future gentoo git can never rebase its commit |
| 12 |
>> history, why chance it? |
| 13 |
> |
| 14 |
> I think that the reality is that we're going to have a million dress |
| 15 |
> rehearsals before we do the real thing. Apparently right now the |
| 16 |
> conversion isn't quite right, and we can't validate that it is right |
| 17 |
> either. I don't see any harm in having people look into being able to |
| 18 |
> keep the downtime low while others figure out how the migration works |
| 19 |
> in the first place. |
| 20 |
> |
| 21 |
> Dress rehearsals don't need to even be announced. You just grab a |
| 22 |
> snapshot of cvs at some random time and convert it and test it. Then |
| 23 |
> you grab another snapshot at a later moment in time and try to use it |
| 24 |
> to catch up the converted repository. Then you test it all again. If |
| 25 |
> you can do that on demand without issue then I'd say we're ready to |
| 26 |
> go. |
| 27 |
|
| 28 |
If I have time this week, I'll throw a script together that does this |
| 29 |
automatically. Which could then be stuffed in a cron job somewhere. |
| 30 |
(Running out the door...will read the rest of the email later.) |
| 31 |
|
| 32 |
-- |
| 33 |
:wq |
Archives