git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: Olivier Galibert <galibert@pobox.com>
Cc: Peter Baumann <Peter.B.Baumann@stud.informatik.uni-erlangen.de>,
	git@vger.kernel.org
Subject: Re: git-show --stat on first commit
Date: Tue, 21 Nov 2006 13:42:38 -0500	[thread overview]
Message-ID: <20061121184238.GC22283@spearce.org> (raw)
In-Reply-To: <20061121183853.GA61605@dspnet.fr.eu.org>

Olivier Galibert <galibert@pobox.com> wrote:
> On Tue, Nov 21, 2006 at 06:11:19PM +0100, Peter Baumann wrote:
> > And I think handling this behaviour as a config option is the right thing,
> > because most of the time if someone imports a project into git he
> > will import the whole history, especially if he is using one of the
> > cvs/svn importers. A "halfway import" as seen in the kernel repo is a
> > special case and it is unlikely seen again.
> 
> Not all projects run on a public VCS.  Hell, not all projects run on a
> VCS at all.  And in the CVS case, you don't always have enough access
> to actually download the repository, which afaik is needed for
> importing.

There is a tool floating around the 'net that will download
a CVS repository and recreate the ,v files locally for you.
cvssuck appears to be its name:

  http://freshmeat.net/projects/cvssuck/

-- 

  reply	other threads:[~2006-11-21 18:45 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 13:41 git-show --stat on first commit Andy Parkins
2006-11-21 14:01 ` Jakub Narebski
2006-11-21 14:09 ` Santi Béjar
2006-11-21 16:08   ` Peter Baumann
2006-11-21 16:18     ` Jakub Narebski
2006-11-21 17:16       ` Peter Baumann
2006-11-21 18:14       ` Horst H. von Brand
2006-11-21 16:31     ` Linus Torvalds
2006-11-21 16:47       ` Shawn Pearce
2006-11-21 17:11       ` Peter Baumann
2006-11-21 17:20         ` Linus Torvalds
2006-11-21 18:38         ` Olivier Galibert
2006-11-21 18:42           ` Shawn Pearce [this message]
2006-11-21 19:05           ` Petr Baudis
2006-11-21 18:06       ` Petr Baudis
2006-11-21 18:16         ` Jakub Narebski
2006-11-21 18:21           ` Petr Baudis
2006-11-21 18:34             ` Shawn Pearce
2006-11-21 18:39             ` Andy Parkins
2006-11-21 18:48               ` Petr Baudis
2006-11-21 18:52                 ` Shawn Pearce
2006-11-21 19:04                   ` Petr Baudis
2006-11-21 19:31             ` Junio C Hamano
2006-11-21 20:03               ` Jakub Narebski
2006-11-23  9:25                 ` Andy Parkins
2006-11-24  7:49                   ` Jakub Narebski
2006-11-23  9:36               ` [PATCH] config option core.showroot to enable showing the diff of the root commit Peter Baumann
2006-11-23 20:52                 ` Junio C Hamano
2006-11-23 23:34                   ` Peter Baumann
2006-11-24  0:18                     ` Junio C Hamano
2006-11-24  1:30                       ` Junio C Hamano
2006-11-24  7:53                         ` Peter Baumann
2006-11-24  8:54                           ` Junio C Hamano
2006-11-24  9:04                             ` Peter Baumann
2006-11-21 18:39       ` git-show --stat on first commit Carl Worth
2006-11-21 19:15       ` Junio C Hamano

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=20061121184238.GC22283@spearce.org \
    --to=spearce@spearce.org \
    --cc=Peter.B.Baumann@stud.informatik.uni-erlangen.de \
    --cc=galibert@pobox.com \
    --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.
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).