From: Junio C Hamano <gitster@pobox.com>
To: Jamey Sharp <jamey@minilop.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>, Jakub Narebski <jnareb@gmail.com>,
Bert Wesarg <bert.wesarg@googlemail.com>,
git@vger.kernel.org, Josh Triplett <josh@joshtriplett.org>
Subject: Re: [PATCHv8 1/4] Fix prefix handling in ref iteration functions
Date: Tue, 07 Jun 2011 17:17:56 -0700 [thread overview]
Message-ID: <7v4o4141mz.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1307487890-3915-2-git-send-email-jamey@minilop.net> (Jamey Sharp's message of "Tue, 7 Jun 2011 16:04:47 -0700")
This round does fix the ".have" issues, but with the --namespace patch
later in the series, it seems to break the same test, by filtering .have
entries with "refs/" prefix.
> Commit by Josh Triplett and Jamey Sharp.
Didn't I ask you to remove this?
Please pick which one of you would be the primary contact for each patch.
I know you said you two did these commits sitting side-by-side, but the
thing is, we simply don't care, and "git shortlog" and the author list you
can see at http://www.git-scm.com/about don't, either.
It is somewhat irritating having to re-edit the log message (not just this
part, but what have been queued were retitled, reflowed and reworded to
match the style of other commits in the project better) over and over
again.
next prev parent reply other threads:[~2011-06-08 0:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 23:04 [PATCHv8 0/4] Support ref namespaces Jamey Sharp
2011-06-07 23:04 ` [PATCHv8 1/4] Fix prefix handling in ref iteration functions Jamey Sharp
2011-06-08 0:17 ` Junio C Hamano [this message]
2011-06-08 1:40 ` Josh Triplett
2011-06-07 23:04 ` [PATCHv8 2/4] Add infrastructure for ref namespaces Jamey Sharp
2011-06-07 23:04 ` [PATCHv8 3/4] Support ref namespaces for remote repositories via upload-pack and receive-pack Jamey Sharp
2011-06-07 23:04 ` [PATCHv8 4/4] Add documentation for ref namespaces Jamey Sharp
2011-06-08 15:19 ` Marc Branchaud
2011-06-15 11:18 ` Painless namespaces design Jiang Xin
2011-06-15 14:00 ` Shawn Pearce
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=7v4o4141mz.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=jamey@minilop.net \
--cc=jnareb@gmail.com \
--cc=josh@joshtriplett.org \
--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 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).