From: Junio C Hamano <junkio@cox.net>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org, seth@hand.yhbt.net
Subject: Re: [RFC/PATCH 2/2] git-svn: rename 'commit' command to 'set-tree'
Date: Sat, 16 Dec 2006 05:26:03 -0800 [thread overview]
Message-ID: <7vbqm4ezv8.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <11662558902535-git-send-email-normalperson@yhbt.net> (Eric Wong's message of "Fri, 15 Dec 2006 23:58:08 -0800")
Eric Wong <normalperson@yhbt.net> writes:
> 'set-tree' probably accurately describes what the command
> formerly known as 'commit' does.
>
> I'm not entirely sure that 'dcommit' should be renamed to 'commit'
> just yet... Perhaps 'push' or 'push-changes'?
I think Pasky did such a three-way rename to avoid breaking
people's fingers. I thought it was a reasonable transition
strategy, but some people might say its only effect was to break
people's fingers not just once but twice, so Pasky himself
and/or Cogito users may have some input on this.
We are talking about major UI change between 1.4 series and
v1.5.0 on the core Porcelain-ish side, so if you feel confident
that things would settle down in a month or so in the git-svn
front, it may be a good idea to roll sweeping changes into the
same timeframe.
next prev parent reply other threads:[~2006-12-16 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 20:21 [RFC] requiring Perl SVN libraries for git-svn Eric Wong
2006-12-13 21:17 ` Randal L. Schwartz
2006-12-15 16:02 ` Seth Falcon
2006-12-15 18:44 ` Eric Wong
2006-12-15 21:06 ` Seth Falcon
2006-12-16 7:58 ` [RFC/PATCH 1/2] git-svn: remove support for the svn command-line client Eric Wong
2006-12-16 7:58 ` [RFC/PATCH 2/2] git-svn: rename 'commit' command to 'set-tree' Eric Wong
2006-12-16 13:26 ` Junio C Hamano [this message]
2006-12-16 21:44 ` Eric Wong
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=7vbqm4ezv8.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=seth@hand.yhbt.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.