From: Peter Baumann <waste.manager@gmx.de>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: git@vger.kernel.org
Subject: Re: Problems with git-svnimport
Date: Wed, 4 Jul 2007 00:19:55 +0200 [thread overview]
Message-ID: <20070703221955.GG4580@xp.machine.xx> (raw)
In-Reply-To: <loom.20070703T214211-88@post.gmane.org>
On Tue, Jul 03, 2007 at 07:45:12PM +0000, Matthias Urlichs wrote:
> Johannes Schindelin <Johannes.Schindelin <at> gmx.de> writes:
>
> > Let's deprecate git-svnimport, once for all.
> >
> > git-svn should work much better.
> >
> In other words, you volunteer to fold everything that git-svnimport can do into
> git-svn? The last time I checked, neither was a feature-complete subset of the
> other...
>
> If so: don't let me hold you back. ;-)
>
May I ask what is missing in git-svn to replace git-svnimport? As I
can't think of anything which is missing in git-svn.
-Peter
next prev parent reply other threads:[~2007-07-03 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 21:42 Problems with git-svnimport Alex R.M. Turner
2007-06-07 22:29 ` Johannes Schindelin
2007-07-03 19:45 ` Matthias Urlichs
2007-07-03 22:19 ` Peter Baumann [this message]
2007-06-08 10:56 ` Martin Langhoff
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=20070703221955.GG4580@xp.machine.xx \
--to=waste.manager@gmx.de \
--cc=git@vger.kernel.org \
--cc=smurf@smurf.noris.de \
/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).