| 1 |
On Sun, 9 Aug 2015 12:04:43 +0200 Francisco Blas Izquierdo Riera |
| 2 |
(klondike) wrote: |
| 3 |
> El 09/08/15 a las 12:02, Mike Frysinger escribió: |
| 4 |
> > On 09 Aug 2015 11:31, Marc Schiffbauer wrote: |
| 5 |
> >> * Michael Weber schrieb am 09.08.15 um 11:00 Uhr: |
| 6 |
> >>> On 08/09/2015 07:36 AM, Robin H. Johnson wrote: |
| 7 |
> >>>> I'm only 90% sure that everything works, but I've spent almost the |
| 8 |
> >>>> entire day on it, and there's more to go tomorrow. |
| 9 |
> >>> Thanks a lot! |
| 10 |
> >>> |
| 11 |
> >>> use case: my cvs tree had uncommitted ebuild work (yes, you caught me |
| 12 |
> >>> actually doing something). |
| 13 |
> >>> now `cvs diff` no longer works, how can i track down my local changes? |
| 14 |
> >>> besides diffing against git tree, brain memory aka shell history and |
| 15 |
> >>> find -newer? |
| 16 |
> >> I'd say: |
| 17 |
> >> |
| 18 |
> >> - tar your *.ebuild and files/* stuff away |
| 19 |
> >> - then "git clone" the new git repo. |
| 20 |
> >> - untar your files in the new git repo |
| 21 |
> >> - use "git diff" |
| 22 |
> > there will be a ton of cvs keyword noise in there though. need to run |
| 23 |
> > a sed on the files to clear it out. |
| 24 |
> > |
| 25 |
> > it also will include noise where your local checkout was behind the latest |
| 26 |
> > tree, so it'll only really work if you ran `cvs up` in the whole tree just |
| 27 |
> > before it was shutdown. |
| 28 |
> > -mike |
| 29 |
> Out of curiosity, is it impossible to have a read only CVS server with |
| 30 |
> the state at the time of the freeze? |
| 31 |
|
| 32 |
Seconded here. Read-only CVS should not consume much resources, but |
| 33 |
will facilitate migration. |
| 34 |
|
| 35 |
Best regards, |
| 36 |
Andrew Savchenko |
Archives