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