Re: State of the CVS conversion

[sfeam <sf...@us...>]

On Saturday, 04 November 2017 10:30:34 Eric S. Raymond wrote:
> "Bastian Märkisch" <bma...@we...>:
> > There are a few cases which we probably would like to fix because the
> > ChangeLog was modified in an "atypical" way.  Should this be done now
> > or can this be corrected after the conversion (sorry, not really 
> > familiar with git yet)?
> 
> It can be done either way.  Safest to do it before the cutover, so the
> changest get recorded in reconvert and not lost if we do some other
> modification.

Could you provide a recipe for making such a correction?

After I tried to make a pass over the ChangeLogs fixing typos etc
on 13 October, I thought you and Dan told me that it was wasted 
effort because the conversion script looks at the text originally
committed, not at the corrected text.
So how does one fix such a problem?

Meanwhile, I've begun trying to actually use the converted
repository on sf.net.    I'm having mixed success, but so far I am
attributing that to my general cluelessness about the best 
sequence of commands or procedures to 
  - check out 
  - modify files
  - commit 
  - push
against a previously-existing branch.   I can make this work with the
assistance of gitk but so far have failed to make it work from the
command line.

I've pushed some trivial patches against branch-5-2-stable so
the git content has already  diverged in minor ways from the cvs version.
No real harm will be done if the conversion is re-executed with fewer
rough corners.  Just let me know if that's the plan.

Oh - one other question.
Can other people actually see the files inside branch-X-X-stable
via the SourceForge web view interface?   I find that in order to
make this work I have to hit the "Repository Refresh" button.
Thing is, that button is in a tab marked "admin-git-main" that 
I don't think normal users can see.  

	Ethan