|
From: Bastian M. <bma...@we...> - 2017-10-16 06:43:09
|
To my knowledge there are a number of files in the CVS repository which are treated as text, but shouldn't be. They either have to have a distinct end-of-line marker (like win/gnuplot.iss) or they really contain binary data (applies e.g. to some files in the demo directory). That typically isn't a problem in *nix systems, but on Windows because some CVS programs try to be clever in adjusting the EOL marker. Can that be taken care of? If yes, I can come up with a list. Please excuse my ignorance if this isn't an issue with git at all. Bastian > -----Ursprüngliche Nachricht----- > Von: Eric S. Raymond [mailto:es...@th...] > Gesendet: Sonntag, 15. Oktober 2017 21:01 > An: To...@th...:sfeam <sf...@us...> > Cc: gnu...@li... > Betreff: Repo conversion procedure is basically done > > I can now produce a git version of the GNUPLOT repository with the following > properties: > > (1) Content correctness, as previously discussed. > > (2) All committer fields are full DVCS-style IDs. > > (3) Over 3100 other authorship attributions are recovered from > ChangeLog files. > > (3) The faq module contents is merged in. > > (4) Three very early releases that servived only as tarballs are > glued to the tail of the repository. > > (5) An annotated tag marks the comversion point. > > I think this is basically done, unless Ethan wants me to glue more tarballs to its > tail. It looks pretty good in gitk. > (snip) |