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