git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hommey <mh@glandium.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Allow to control the namespace for replace refs
Date: Fri, 12 Jun 2015 05:46:11 +0900	[thread overview]
Message-ID: <20150611204611.GA10114@glandium.org> (raw)
In-Reply-To: <xmqq1thigtsd.fsf@gitster.dls.corp.google.com>

On Thu, Jun 11, 2015 at 08:16:02AM -0700, Junio C Hamano wrote:
> Mike Hommey <mh@glandium.org> writes:
> 
> > I do agree that this is all confusing, but allow me to point out that
> > it's already plenty confusing: "namespace" is a term that has been used to
> > designate a generic kind of namespace *and* refs/namespaces. See for
> > example:
> >
> > https://github.com/git/git/blob/master/Documentation/git-describe.txt#L39
> > https://github.com/git/git/blob/master/Documentation/git-fetch.txt#L113
> > https://github.com/git/git/blob/master/Documentation/git-filter-branch.txt#L36
> > (note how this one is specifically about refs/replace/)
> > there are many more.
> 
> "One more breakage does not hurt" is not something we want to see.

I won't disagree here, but we are in desperate need for a word for those
namespaces that aren't refs/namespaces, and stick to it (independently
of the replace patch), but I've never seen one.

Mike

  reply	other threads:[~2015-06-11 20:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  1:47 [PATCH] Allow to control the namespace for replace refs Mike Hommey
2015-06-11  4:55 ` Junio C Hamano
2015-06-11  5:13   ` Mike Hommey
2015-06-11 15:16     ` Junio C Hamano
2015-06-11 20:46       ` Mike Hommey [this message]
2015-06-11 20:55         ` Junio C Hamano
2015-06-11 21:34       ` [PATCH v2] Allow to control where the replace refs are looked for Mike Hommey
2015-06-12 22:29         ` Junio C Hamano
2015-06-12 22:36           ` 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=20150611204611.GA10114@glandium.org \
    --to=mh@glandium.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).