Thread (1 message) 1 message, 1 author, 2016-06-15

Re: Imports without Tariffs

From: Michael Witten <hidden>
Date: 2016-06-15 22:43:41

On 12 Oct 2007, at 4:36:29 PM, mfwitten@MIT.EDU wrote:
To make things simple, I think all of the necessary machinery
should be put into git-cvsimport.

The user should first git-cvsexportcommit as necessary.

Now that I have considered, it makes more sense to put the
machinery in git-cvsexportcommit.

The user could use a -b flag to specify the git branch to push
into after the cvs commit occurs, and git-cvsexportcommit would
update the .git/SCM_IMPORT file (changed from CVS_IMPORT).

Of course, this introduces other troubles.

Sometimes I run cvsexportcommit using a git repo on another server.
So perhaps one should also be able to use cvsexportcommit for just
pushing and editing the .git/SCM_IMPORT file.

That way it's possible to update CVS and then notify any other git
repo by hand.

Michael
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help