git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Nick Woolley <nickwoolley@yahoo.co.uk>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git-cvs script
Date: Sat, 30 May 2009 16:33:17 -0700	[thread overview]
Message-ID: <7vr5y6xj2a.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4A213793.3030205@yahoo.co.uk> (Nick Woolley's message of "Sat\, 30 May 2009 14\:41\:39 +0100")

Nick Woolley <nickwoolley@yahoo.co.uk> writes:

> I have script which wraps git-cvsimport and git-cvsexport, called "git-cvs".
>
> The main aim of the script is to automate the steps for tracking a CVS
> repository with the git-cvs* commands.

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.

> It's not currently as sophisticated as git-svn,...
> ...
>  - 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 ;-)

  reply	other threads:[~2009-05-30 23:34 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 [this message]
2009-06-01 10:47   ` Nick Woolley
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=7vr5y6xj2a.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nickwoolley@yahoo.co.uk \
    /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).