From: Michael Witten <mfwitten@MIT.EDU>
To: git@vger.kernel.org
Subject: Re: Imports without Tariffs
Date: Sat, 13 Oct 2007 00:44:54 -0400 [thread overview]
Message-ID: <C30A314A-C258-4585-86FD-C1158ACA85C2@mit.edu> (raw)
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
next prev parent reply other threads:[~2007-10-13 4:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 20:36 Imports without Tariffs mfwitten
2007-10-13 2:49 ` Jeff King
[not found] ` <3B7796D6-5901-40B0-B3FC-70642AC50B08@mit.edu>
2007-10-13 4:44 ` Michael Witten [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-13 4:01 (unknown), Michael Witten
2007-10-13 4:07 ` your mail Jeff King
[not found] ` <1240801C-F4CC-4290-8C3D-2038F1957DF3@MIT.EDU>
2007-10-13 4:39 ` Imports without Tariffs Michael Witten
2007-10-13 7:57 ` Jeff King
2007-10-13 23:04 ` Michael Witten
2007-10-14 16:40 ` Jeff King
2007-10-14 22:10 ` Michael Witten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C30A314A-C258-4585-86FD-C1158ACA85C2@mit.edu \
--to=mfwitten@mit.edu \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).