From: Jakub Narebski <jnareb@gmail.com>
To: Jeff King <peff@peff.net>
Cc: 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, 08 Jun 2011 10:25:27 -0700 (PDT) [thread overview]
Message-ID: <m3hb80dynr.fsf@localhost.localdomain> (raw)
In-Reply-To: <20110607214532.GB7663@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> I find the all-caps ugly, and it is part of what confuses them with
> HEAD. At the same time, we are using the same namespace that ref lookup
> uses. So calling it "worktree" might be too ambiguous. I tried to avoid
> using "--worktree" because I wanted to make it clear that these were
> ordered arguments, not options.
Perhaps we can use some character that is forbidden in ref names,
doesn't make trouble when doing allowed operations on said refs, won't
confuse user, and is not trouble with shell... ehhh...
* @{wtree} would confuse users that it has something to do with reflog
* [tree] would be trouble with some shells
* ~tree~ looks a bit strange, might be trouble with username expansion
* :tree: might be mistaken for 'tree:' in index
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-06-08 17:28 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 [this message]
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
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=m3hb80dynr.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--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 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).