All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Thomas Rast <trast@inf.ethz.ch>
Cc: Duy Nguyen <pclouds@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Michael Haggerty <mhagger@alum.mit.edu>
Subject: Re: What's cooking in git.git (May 2013, #04; Wed, 15)
Date: Tue, 21 May 2013 08:27:43 -0700	[thread overview]
Message-ID: <7vy5b8qro0.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <87a9nobyae.fsf@linux-k42r.v.cablecom.net> (Thomas Rast's message of "Tue, 21 May 2013 09:13:45 +0200")

Thomas Rast <trast@inf.ethz.ch> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>
>> In addition to your topic, it may be a good idea to notice this at
>> the Porcelain level (e.g. "checkout -b" and "branch", but not at the
>> "update-ref" level) and warn or even die if a Porcelain tries to
>> create a branch with such a name.
>
> But if we're going there and deprecating some ways of naming refs,

This is not about deprecating but is discouraging a confusing use at
the Porcelain level (i.e. enforcing one policy decision that may not
apply to those who wrote their own workflow using plumbing commands,
knowing and following the "full 40-hex is taken as an object name,
not a dwimmed ref" rule---to them there is no ambiguities).

I think I see where you are going and I do not necessarily disagree
with that, but it is a separate topic.

> please also disallow some other funny things in the same go.  Michael
> suggested this earlier in some thread: the fewer ways we have of legally
> spelling refnames, the more syntax is available for revision syntax.

  reply	other threads:[~2013-05-21 15:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 23:42 What's cooking in git.git (May 2013, #04; Wed, 15) Junio C Hamano
2013-05-16  0:25 ` David Aguilar
2013-05-20 10:18 ` Duy Nguyen
2013-05-20 16:17   ` Junio C Hamano
2013-05-21  7:13     ` Thomas Rast
2013-05-21 15:27       ` Junio C Hamano [this message]
2013-05-27 10:36     ` Duy Nguyen
2013-05-28 21:25       ` Junio C Hamano
2013-05-20 23:08 ` Felipe Contreras

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=7vy5b8qro0.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    --cc=pclouds@gmail.com \
    --cc=trast@inf.ethz.ch \
    /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.