git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Imports without Tariffs

From
Michael Witten <mfwitten@mit.edu>
Date
Oct 13, 2007, 04:44 UTC
Message-ID
<C30A314A-C258-4585-86FD-C1158ACA85C2@mit.edu>
In-Reply-To
<3B7796D6-5901-40B0-B3FC-70642AC50B08@mit.edu>
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
Previous: Jeff King
Message 3 of 3 in “Imports without Tariffs”
  1. mfwitten@mit.eduOct 12, 2007
  2. Jeff KingOct 13, 2007
  3. Michael WittenOct 13, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.