git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Steffen Prohaska" <prohaska@zib.de>, "Eric Blake" <ebb9@byu.net>,
	m4-patches@gnu.org, "Jim Meyering" <jim@meyering.net>,
	git@vger.kernel.org
Subject: Re: cvsimport bug on branches [was: conversion to git]
Date: Sat, 22 Sep 2007 12:05:38 +1200	[thread overview]
Message-ID: <46a038f90709211705y351dbe6cp50c249dc0fcfd5a0@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0709210840190.16478@woody.linux-foundation.org>

On 9/22/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> The big advantage of git-cvsimport is that it can do incremental imports,

Indeed. And it can take over incrementals on a GIT repo initially
imported by parsecvs or cvs2git. That's the recommended practice for
tracking non-trivial CVS repos -- IOWs "that's what I do" ;-)

cheers,


m

      parent reply	other threads:[~2007-09-22  0:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <loom.20070920T010842-272@post.gmane.org>
2007-09-21  1:17 ` cvsimport bug on branches [was: conversion to git] Eric Blake
2007-09-21  5:18   ` Steffen Prohaska
2007-09-21 15:42     ` Linus Torvalds
2007-09-21 17:15       ` Robin Rosenberg
2007-09-21 20:22         ` Johannes Schindelin
2007-09-21 20:42           ` Robin Rosenberg
2007-09-21 21:12             ` Johannes Schindelin
2007-09-21 23:16               ` Robin Rosenberg
2007-09-22  8:07                 ` fromcvs installation [was: cvsimport bug on branches [was: conversion to git]] Steffen Prohaska
2007-09-22 15:08                   ` Simon 'corecode' Schubert
2007-09-22  0:05       ` Martin Langhoff [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46a038f90709211705y351dbe6cp50c249dc0fcfd5a0@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=ebb9@byu.net \
    --cc=git@vger.kernel.org \
    --cc=jim@meyering.net \
    --cc=m4-patches@gnu.org \
    --cc=prohaska@zib.de \
    --cc=torvalds@linux-foundation.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.
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 NNTP newsgroup(s).