From: Nick Woolley <nickwoolley@yahoo.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git-cvs script
Date: Mon, 01 Jun 2009 11:47:10 +0100 [thread overview]
Message-ID: <4A23B1AE.1070000@yahoo.co.uk> (raw)
In-Reply-To: <7vr5y6xj2a.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> If I recall correctly, the above is in line with the original spirit of
> how git-cvsexportcommit was envisioned to be used by its original authors.
>
> That is, the import side is more or less satisfactory done in the sense
> that it deserved a short and sweet command name, but the export side is
> not as finished as the import side is, and you have to drive it more
> explicitly by telling what commit to send back to the CVS side. Building
> on top of it so the tool keeps track of what needs to be sent, like git-svn
> allows users to do, would be the right thing to do.
Ok - thanks.
Apart from fixing significant bugs, for now I've been avoiding making any major
changes to git-cvsexportcommit git-cvsimport, since understanding their guts
takes a significant amount of time and effort.
On the other hand, if I ever did, then currently git-cvsexportcommit and
git-cvsimport are separate commands. I would imagine they would want to share
some code, like "push" and "pull" operations do in git-cvs. Is that
possible/encouraged in the current scheme? (e.g. "use Git::CVS" - I notice there
is a Git.pm in the source.) Or would this need to be done by rolling it all
into a single command as git-svn seems to do it?
>> - Is this at all useful to anyone else in it's current form?
>
> I have to admit that it won't be to me (because I do not interact with CVS
> myself) but I don't count ;-)
An enviable position to be in, sir.
N
next prev parent reply other threads:[~2009-06-01 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 13:41 [RFC] git-cvs script Nick Woolley
2009-05-30 23:33 ` Junio C Hamano
2009-06-01 10:47 ` Nick Woolley [this message]
2009-05-31 7:42 ` Alex Bennee
2009-06-01 9:47 ` Nick Woolley
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=4A23B1AE.1070000@yahoo.co.uk \
--to=nickwoolley@yahoo.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).