All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Scott Chacon <schacon@gmail.com>,
	Michael Nahas <mike@nahas.com>
Subject: Re: [RFC/PATCH] git put: an alternative to add/reset/checkout
Date: Wed, 8 Jun 2011 20:57:47 +0200	[thread overview]
Message-ID: <201106082057.48139.jnareb@gmail.com> (raw)
In-Reply-To: <vpq62ogkxs0.fsf@bauges.imag.fr>

Matthieu Moy wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
> > Matthieu Moy wrote:
> >> Jeff King <peff@peff.net> writes:
> >> > On Wed, Jun 08, 2011 at 07:28:35PM +0200, Matthieu Moy wrote:
> >> >> > Jeff King <peff@peff.net> writes:
> >> >> >
> >> >> > * @{wtree} would confuse users that it has something to do with reflog
> >> >> 
> >> >> Well, we already have @{upstream} ...
> >> >
> >> > Yes, but like all of the @{} things, it's a modifier for the left-hand
> >> > side. So "master@{upstream}" is meaningful, and "@{upstream}" is the
> >> > same as "HEAD@{upstream}".
> >> >
> >> > What does "master@{wtree}" mean?
> >> 
> >> Nothing, but then we already have @{-1} ;-).
> >
> > That's actually HEAD reflog.
> 
> Yes, but neither HEAD@{-1} nor master@{-1} work. So we have one instance
> of @{...} which is unrelated from reflog, and another which isn't a
> suffix. @{wtree} would be both.

But both are about refs (upstream of a ref, or previously checked-out ref).
@{wtree} ain't.

-- 
Jakub Narebski
Poland

  reply	other threads:[~2011-06-08 18:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 20:06 [RFC/PATCH] git put: an alternative to add/reset/checkout Jeff King
2011-06-07 21:04 ` Junio C Hamano
2011-06-07 21:45   ` Jeff King
2011-06-08  3:07     ` Michael Nahas
2011-06-08 17:25     ` Jakub Narebski
2011-06-08 17:28       ` Matthieu Moy
2011-06-08 17:30         ` Jeff King
2011-06-08 17:34           ` Matthieu Moy
2011-06-08 17:50             ` Jakub Narebski
2011-06-08 18:01               ` Matthieu Moy
2011-06-08 18:57                 ` Jakub Narebski [this message]
2011-06-10 12:38       ` Nguyen Thai Ngoc Duy
2011-06-08 15:18 ` Nguyen Thai Ngoc Duy
2012-01-23 10:32 ` Nguyen Thai Ngoc Duy
2012-01-23 13:53   ` Michael Nahas
2012-01-23 14:35     ` Nguyen Thai Ngoc Duy
2012-01-23 14:56       ` Michael Nahas
2012-01-23 18:10         ` Junio C Hamano

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=201106082057.48139.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mike@nahas.com \
    --cc=peff@peff.net \
    --cc=schacon@gmail.com \
    /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.