From: Josh Triplett <josh@joshtriplett.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jamey Sharp <jamey@minilop.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>, Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCHv5 2/4] Add infrastructure for ref namespaces
Date: Fri, 3 Jun 2011 16:43:57 -0700 [thread overview]
Message-ID: <20110603234357.GA2170@leaf> (raw)
In-Reply-To: <7vd3iua4bm.fsf@alter.siamese.dyndns.org>
On Fri, Jun 03, 2011 at 04:22:05PM -0700, Junio C Hamano wrote:
> Jamey Sharp <jamey@minilop.net> writes:
>
> > Note that namespaces which include a / will expand to a hierarchy of
> > namespaces; for example, GIT_NAMESPACE=foo/bar will store refs under
> > refs/namespaces/foo/refs/namespaces/bar/. This makes GIT_NAMESPACE
> > behave hierarchically, and avoids ambiguity with namespaces such as
> > foo/refs/heads.
>
> I would have expected that this explanation would be improved after you
> having to answer my question on the list. Otherwise it was a wasted
> effort, for both me (asking) and you (answering).
Just missed it when re-spinning the series. Will re-send with an
updated commit message for that patch.
> > This adds the infrastructure for ref namespaces: handling the
> > GIT_NAMESPACE environment variable and --namespace option, and iterating
> > over refs in a namespace. Subsequent commits use this infrastructure to
> > implement the user-visible support for ref namespaces.
> >
> > Commit by Josh Triplett and Jamey Sharp.
>
> Also please drop that "Commit by ...". We can read Sign-off.
Signed-off-by doesn't quite have the right meaning, since normally a
chain of signoffs just indicates the chain of review, not necessarily
authorship. We brought this up at one point previously[1], and Jonathan
Nieder pointed to previous discussions about this, with the apparent
conclusion to use another pseudo-header to indicate co-authorship.
(Also why we originally put it in the same paragraph as the
signed-off-by.) Documentation/SubmittingPatches also mentions the
possibility of adding extra pseudo-headers similar to Signed-off-by, as
appropriate.
We really did write these patches (and commit messages) sitting right
next to each other and switching off with the same keyboard. :)
- Josh Triplett and Jamey Sharp
[1] http://bugs.debian.org/451880
next prev parent reply other threads:[~2011-06-03 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 21:29 [PATCHv5 0/4] Support ref namespaces Jamey Sharp
2011-06-03 21:29 ` [PATCHv5 1/4] Fix prefix handling in ref iteration functions Jamey Sharp
2011-06-03 21:29 ` [PATCHv5 2/4] Add infrastructure for ref namespaces Jamey Sharp
2011-06-03 23:22 ` Junio C Hamano
2011-06-03 23:43 ` Josh Triplett [this message]
2011-06-03 21:29 ` [PATCHv5 3/4] Support ref namespaces for remote repositories via upload-pack and receive-pack Jamey Sharp
2011-06-03 21:29 ` [PATCHv5 4/4] Add documentation for ref namespaces Jamey Sharp
2011-06-03 23:24 ` [PATCHv5 0/4] Support " Junio C Hamano
2011-06-03 23:48 ` Josh Triplett
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=20110603234357.GA2170@leaf \
--to=josh@joshtriplett.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jamey@minilop.net \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
--cc=spearce@spearce.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 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.