git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yasushi SHOJI <yashi@atmark-techno.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: RFC: s/git-merge-base/git-find-common-ancestor/g
Date: Sun, 11 Sep 2005 16:02:19 +0900	[thread overview]
Message-ID: <874q8s6q9w.wl@mail2.atmark-techno.com> (raw)
In-Reply-To: <7virxbtder.fsf@assigned-by-dhcp.cox.net>

At Thu, 08 Sep 2005 15:14:52 -0700,
Junio C Hamano wrote:
> 
> The "master" branch post 0.99.6 already has the renamed tools
> with backward compatibility symlinks.  I'll be sending a
> patch to address an issue raised by some people separately to
> see what the list thinks, and also will attempt to send out a
> patch for the Pasky and Catalin heads later this week.  Also
> I'll remove the ancient backward compatible environment variable
> names from gitenv.c.

everything seems very consistent indeed, except one command:

   git-merge-base

I've already got used to it. but, at first, the name gave me the
impression that it merge the current branch with given base point.

the current documentation says:

   Finds as good a common ancestor as possible for a merge

so would it be better to rename it to:

   git-find-common-ancestor

That's what the command does after all.
--
         yashi

  parent reply	other threads:[~2005-09-11  7:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08  0:08 GIT 0.99.6 Junio C Hamano
2005-09-08 22:14 ` Tool renames and 'ls-files -t' output Junio C Hamano
2005-09-09  9:20   ` Post 0.99.7 preperation patches Junio C Hamano
2005-09-12  1:26     ` Petr Baudis
2005-09-11  7:02   ` Yasushi SHOJI [this message]
2005-09-11  7:38     ` RFC: s/git-merge-base/git-find-common-ancestor/g Junio C Hamano
2005-09-11  8:40       ` [PATCH] Rename git-merge-base to git-find-merge-base Yasushi SHOJI
2005-09-09  0:58 ` [RFC/Patch] Tool rename fallout fix Junio C Hamano
2005-09-17 16:43 ` No GIT 0.99.7 today Junio C Hamano
2005-09-18 23:37 ` [ANNOUNCE] GIT 0.99.7 Junio C Hamano
2005-09-18 23:40   ` What to expect after " Junio C Hamano
2005-09-19  1:30     ` Linus Torvalds
2005-09-19  2:02       ` Linus Torvalds
2005-09-19  9:56       ` Johannes Schindelin
2005-09-19 14:15       ` Joachim B Haga
2005-09-19 15:06         ` Linus Torvalds
2005-09-19  6:02     ` Anton Altaparmakov
2005-09-19  7:35     ` Matthias Urlichs
2005-09-19  8:25       ` Junio C Hamano
2005-09-19  8:36         ` Petr Baudis
2005-09-19 14:34         ` Linus Torvalds
2005-09-19  1:14   ` [ANNOUNCE] Cogito-0.15 Petr Baudis
2005-09-19 23:15     ` Pavel Machek
2005-09-20  0:35       ` Petr Baudis
2005-09-20  0:51       ` Linus Torvalds
2005-09-19  2:24   ` [ANNOUNCE] GIT 0.99.7 Nigel Cunningham
2005-09-19 12:01     ` Chris White
2005-09-19  6:21       ` Alan Chandler

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=874q8s6q9w.wl@mail2.atmark-techno.com \
    --to=yashi@atmark-techno.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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 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).