git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: Sam Vilain <sam@vilain.net>, Junio C Hamano <junkio@cox.net>,
	Catalin Marinas <catalin.marinas@gmail.com>,
	Yann Dirson <ydirson@altern.org>,
	git@vger.kernel.org
Subject: Re: [PATCH] Add "stg bury" command, with the functionnality of contrib/stg-sink.
Date: Wed, 18 Apr 2007 22:19:26 +0200	[thread overview]
Message-ID: <200704182219.26410.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704181130330.30721@reaper.quantumfyre.co.uk>

onsdag 18 april 2007 12:33 skrev Julian Phillips:
> On Wed, 18 Apr 2007, Sam Vilain wrote:
> 
> > Julian Phillips wrote:
> >>> Sure... and from my own perspective as a user, I didn't even realise
> >>> what float did until now, and was surprised that "bury" would mean that.
> >>> The metaphor is a stack, not a pool or a sandpit. I don't think those
> >>> terms really assist in understanding, however cute they are.
> >>>
> >>
> >> I find that bury is more natural than float (thinking of a stack of
> >> documents on a desk ...).  But then I don't use stg ...
> >>
> >
> > You demonstrate my point :) by apparently missing that "bury" and
> > "float" are supposed to be the *opposite* of each other.
> 
> I didn't mean to give that impression.  I was aware that they were 
> opposites, but was only commenting on my view of the intuitivness of each.
> 
> I can't really think of a single metaphor where float and bury are both 
> appropriate though.

The stack is transparent, so the "float" comes from thinking of the stack as a 
column (glass pillar) of water with things in it. So I wanted to float patches. I
didn't think too much about the name, it just popped out. At least that is what
I *think* I was thinking at the time.

The logical opposide thing is to "sink" things you don't work to work on.  "bury" 
implies  you don't see things, which just isn't true.

I did consider raise, but then you can raise things only a little. Floating a patch
makes it move all the way to the top.

-- robin

  reply	other threads:[~2007-04-18 20:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 18:27 [PATCH] Add "stg bury" command, with the functionnality of contrib/stg-sink Yann Dirson
2007-04-17 20:42 ` Sam Vilain
2007-04-18  0:02   ` Catalin Marinas
2007-04-18  0:10     ` Junio C Hamano
2007-04-18  2:49       ` Sam Vilain
2007-04-18  7:41         ` Julian Phillips
2007-04-18  8:58           ` Sam Vilain
2007-04-18 10:33             ` Julian Phillips
2007-04-18 20:19               ` Robin Rosenberg [this message]
2007-04-18 20:35                 ` Yann Dirson
2007-04-19  8:59                   ` Karl Hasselström
2007-04-21  9:37                     ` Catalin Marinas
2007-04-21 10:15                       ` Yann Dirson
2007-04-21 11:00                       ` Karl Hasselström

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=200704182219.26410.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=julian@quantumfyre.co.uk \
    --cc=junkio@cox.net \
    --cc=sam@vilain.net \
    --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;
as well as URLs for NNTP newsgroup(s).