Re: Preserving CVS history

On 09/11/14 21:54, Cesar Strauss wrote:
> On 10/29/2014 07:18 PM, Keith Marshall wrote:
>> On 29/10/14 20:42, Cesar Strauss wrote:
>>> It seems the underlying repository is accessible by rsync:
>>>
>>> rsync -avz cygwin.com::src-cvs/src/winsup/w32api srcdir
>>> rsync -avz cygwin.com::src-cvs/src/winsup/mingw srcdir
> 
> I converted the above subset of the Cygwin repository as two Git
> repositories: mingwrt and w32api.

Thanks for doing this.

> I used cvs-fast-export, roughly following this guide:
> 
> DVCS migration HOWTO
> http://www.catb.org/esr/dvcs-migration-guide.html

I know Eric, (yeah, ESR himself), did the conversion for GNU troff from
CVS to git, using the tools he describes there, and that all went quite
smoothly.  If I get a chance, over the next few days, and if I can find
my old CVS sandboxes, I'll clone these...

> The conversion is available temporarily at my SF user project at:
> 
> 1) Web view:
> https://sourceforge.net/u/cstrauss/mingwrt/ci/master/tree/
> https://sourceforge.net/u/cstrauss/w32api/ci/master/tree/
> 
> 2) Read-only git clone:
> git clone git://git.code.sf.net/u/cstrauss/mingwrt
> git clone git://git.code.sf.net/u/cstrauss/w32api

...and check them for consistency; can't promise that I can do better
than checking, at the appropriate release points, against historically
released tarballs, though; nor can I promise a quick turn-around.

> If you agree, I'll publish them both on the MinGW project.

If I don't get back to you, within two weeks at most, please do.

> It seems you resumed development of mingwrt under the legacy branch of
> the WSL repository. Would it make sense to use the mingwrt repository
> instead?

Yes, I think it would.  Even if we do eventually merge it with w32api,
to create a composite similar to WSL, we should maintain the two as
separate sub-repositories of a common overall project; WSL, as it stands
now, appears to be a disaster area best vacated.

> I noticed that the CVS repository contains newer commits that were never
> released in the 3.x branch. For instance, the ChangeLog of mingwrt-3.20
> ends in 08/23/2011 but the CVS history goes up to 08/08/2012.

So, there is some work which never made it into a mingwrt-3.x release;
some of it may even be my own.  We probably want to keep that, or at
least consider merging it with our own work, from after we abandoned the
Cygwin CVS.

> Likewise, the ChangeLog of w32api-3.18 ends in 03/25/2011, but the
> CVS history goes up to 08/10/2012.

I thought our last formal release was w32api-3.17; did Cygwin release
w32api-3.18, before they started to adopt mingw-w64?

> I suppose these additional commits can be reverted in a subsequent
> commit, or erased altogether from the master branch, if you find it
> convenient.

Better to review, and merge as appropriate; it would be a shame to throw
away potentially useful work.

-- 
Regards,
Keith.

------------------------------------------------------------------------------