From: "David Kågedal" <davidk@lysator.liu.se>
To: git@vger.kernel.org
Subject: Re: Draft v1.5.0 release notes
Date: Tue, 02 Jan 2007 08:22:33 +0100 [thread overview]
Message-ID: <87vejp7v0m.fsf@morpheus.local> (raw)
In-Reply-To: 7vlkkm47eg.fsf@assigned-by-dhcp.cox.net
Junio C Hamano <junkio@cox.net> writes:
> * Foreign SCM interfaces
>
> - git-svn now requires the Perl SVN:: libraries, the
> command-line backend was too slow and limited.
>
> - the 'commit' command has been renamed to 'set-tree', and
> 'dcommit' is the recommended replacement for day-to-day
> work.
The second item in this list is misleading. It states that the
"comit" subcommand has been renamed. But I don't believe it's the
"commit" subcommand of the "git" command. So what is it a subcommand
to?
--
David Kågedal
next prev parent reply other threads:[~2007-01-02 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 0:08 Draft v1.5.0 release notes Junio C Hamano
2007-01-02 2:31 ` Steven Grimm
2007-01-02 2:57 ` Shawn O. Pearce
2007-01-02 7:22 ` David Kågedal [this message]
2007-01-02 8:23 ` Shawn O. Pearce
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=87vejp7v0m.fsf@morpheus.local \
--to=davidk@lysator.liu.se \
--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).