From: Junio C Hamano <gitster@pobox.com>
To: Steven Grimm <koreth@midwinter.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Gerrit Pape <pape@smarden.org>,
git@vger.kernel.org
Subject: Re: git-svnimport
Date: Fri, 26 Oct 2007 12:30:16 -0700 [thread overview]
Message-ID: <7vy7dpy8qf.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <47222CB3.9070100@midwinter.com> (Steven Grimm's message of "Fri, 26 Oct 2007 11:06:43 -0700")
Steven Grimm <koreth@midwinter.com> writes:
> Johannes Schindelin wrote:
>>> I'm not sure these are worth fixing, I'd rather suggest to drop
>>> git-svnimport in favor of git-svn, and not installing it in future
>>> versions.
>>>
>> I already proposed this. The outcome was... silent.
>>
>
> Me too, and same reaction.
>
> So I vote we interpret that as, "No objections from anyone."
Likewise.
next prev parent reply other threads:[~2007-10-26 19:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 9:25 git-svnimport Felipe Balbi
2007-10-25 10:56 ` git-svnimport Johannes Schindelin
2007-10-25 11:08 ` git-svnimport Felipe Balbi
2007-10-25 13:04 ` git-svnimport Johannes Schindelin
2007-10-25 22:20 ` git-svnimport Steven Walter
2007-10-25 22:22 ` git-svnimport Johannes Schindelin
2007-10-26 14:55 ` git-svnimport Gerrit Pape
2007-10-26 16:45 ` git-svnimport Johannes Schindelin
2007-10-26 18:06 ` git-svnimport Steven Grimm
2007-10-26 19:30 ` Junio C Hamano [this message]
2007-10-30 14:24 ` [PATCH] no longer install git-svnimport, move to contrib/examples Gerrit Pape
-- strict thread matches above, loose matches on Subject: below --
2007-03-20 18:00 git-svnimport Christian Wiese
2006-02-03 19:29 git-svnimport Jason Harrison
2006-02-04 2:47 ` git-svnimport Jason Riedy
2006-02-04 3:16 ` git-svnimport Martin Langhoff
2006-02-04 3:12 ` git-svnimport 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=7vy7dpy8qf.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=koreth@midwinter.com \
--cc=pape@smarden.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).