Git development
 help / color / mirror / Atom feed
From: Chris Shoemaker <c.shoemaker@cox.net>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Yann Dirson <ydirson@altern.org>,
	Catalin Marinas <catalin.marinas@gmail.com>,
	git@vger.kernel.org
Subject: Re: [RFC PATCH] Rename "bury" back to "sink".
Date: Sat, 5 May 2007 13:35:47 -0400	[thread overview]
Message-ID: <20070505173547.GA3540@pe.Belkin> (raw)
In-Reply-To: <20070505131352.GB3379@diana.vm.bytemark.co.uk>

On Sat, May 05, 2007 at 03:13:53PM +0200, Karl Hasselström wrote:
> On 2007-05-05 00:53:03 +0200, Yann Dirson wrote:
> 
> > Well, it looks like the voices we heard on this naming issue were
> > quite equally cast towards each of the 2 name.
> >
> > Let my vote be to get back to "sink", so the user can easily pair
> > the command with "float". I expect that any previously-silent
> > majoity prefering "bury" will talk now, before Catalin decides if he
> > wants this patch in the next release :)
> 
> Well, my vote is still for "sink"! If it is to be called "stg bury",
> I'd have to vote for changing "stg float" to "stg unearth". :-)

Just my 2.5 cents:

float/sink are clearly related, while I wouldn't associate float/bury
at all.  Also, "bury" is sometimes euphemistic for "kill", so
bury/resurrect is a clear pair.  Anyway, "sink" makes perfect sense to
me.

-chris

      reply	other threads:[~2007-05-05 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 22:53 [RFC PATCH] Rename "bury" back to "sink" Yann Dirson
2007-05-04 23:22 ` Jakub Narebski
2007-05-05 20:13   ` Yann Dirson
2007-05-06 10:49     ` Karl Hasselström
2007-05-13 18:28     ` David Kågedal
2007-05-13 19:06       ` Karl Hasselström
2007-05-05 13:13 ` Karl Hasselström
2007-05-05 17:35   ` Chris Shoemaker [this message]

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=20070505173547.GA3540@pe.Belkin \
    --to=c.shoemaker@cox.net \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kha@treskal.com \
    --cc=ydirson@altern.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