[savannah-help-public] [sr #108761] Please allow Non-Fast-Forward commits for GNU ccd2cue's Git repository

[Assaf Gordon]

Update of sr #108761 (project administration):

                  Status:                    None => In Progress            
             Assigned to:                    None => agn                    

    _______________________________________________________

Follow-up Comment #1:

Hello Bruno,

Savannah's policy is to generally disallow non-fast-forward commits (see
"on-Fast-Forward commits" section at
http://savannah.gnu.org/maintenance/UsingGit/  ).

But since this is a new repository and all but the last few commits (dated
March 5th) also appear in the CVS repository, non-fast-forward commits can be 
temporarily enabled, with the assumption you will commit the same code again,
and no code will be lost.
NFF commits will be disabled again within a day or so

This should allow enough to to fix the problem.

Let us know if there are other issues.

Please not that once significant code is committed to the git repository, NFF
will not be enabled in the future to avoid the possibility of deleting code
from savannah.

- Assaf

P.S.
For cvs-to-git conversions, I can recommend "cvs-fast-export" (
http://www.catb.org/~esr/cvs-fast-export/cvs-fast-export.html ) which also
supports author ID mapping.
I have tested it on many CVS repositories on Savannah it and seems to work
very well.

P.P.S.
Savannah admins,
I've made a copy of the current git repository in
'vsc:/srv/git/ccd2cue.git-disabled', will remove it once the ticket is closed,
and issues of code loss are resolved.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/support/?108761>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/