From: Martin Langhoff <martin.langhoff@gmail.com>
To: Robert Watson <robert.oo.watson@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Do we still need the git command?
Date: Fri, 23 Sep 2005 23:38:31 +1200 [thread overview]
Message-ID: <46a038f905092304384d79d715@mail.gmail.com> (raw)
In-Reply-To: <72499e3b050923042466011c4f@mail.gmail.com>
On 9/23/05, Robert Watson <robert.oo.watson@gmail.com> wrote:
> (2) Different style from CVS/SVN.
That is a plus in my book -- CVS implemented an awful UI, and everyone
else followed. CVS did make use if it in that it discriminated options
to the cvs utility from command options.
> Pros:
> (4) Do not conflict with GNU Interactive Tools. Make the life of
> Debian people easier.
+1! Anything to avoid yet another flamewar in debian-devel ;-) and it
also shows some good manners towards a (mostly forgotten) but good
project. The whole name conflict prompted me to install the GNU
Interactive Tools and run it for a couple of days. Nifty little
"midnight-commander" style utility.
cheers,
martin
next prev parent reply other threads:[~2005-09-23 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 11:24 [RFC] Do we still need the git command? Robert Watson
2005-09-23 11:38 ` Martin Langhoff [this message]
2005-09-23 12:39 ` Sebastian Kuzminsky
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=46a038f905092304384d79d715@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=robert.oo.watson@gmail.com \
/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).