From: Nicolas Pitre <nico@fluxnic.net>
To: Junio C Hamano <junio@pobox.com>
Cc: Nelson Elhage <nelhage@MIT.EDU>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2010, #06; Tue, 23)
Date: Wed, 24 Feb 2010 10:09:53 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1002241004010.1946@xanadu.home> (raw)
In-Reply-To: <7v635nsa37.fsf@alter.siamese.dyndns.org>
On Tue, 23 Feb 2010, Junio C Hamano wrote:
> * ne/pack-local-doc (2010-02-18) 1 commit
> - Documentation: pack-objects: Clarify --local's semantics.
>
> Comments from pack experts?
The patch is fine in the sense that what it modifies was indeed wrong.
However the "even if it appears in the standard input" formulation
should also be fixed as the object list may be specified with a rev spec
on the command line, and not necessarily only via standard input.
Nicolas
next prev parent reply other threads:[~2010-02-24 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 1:20 What's cooking in git.git (Feb 2010, #06; Tue, 23) Junio C Hamano
2010-02-24 2:06 ` Tay Ray Chuan
2010-02-24 6:28 ` Jeff King
2010-02-24 15:09 ` Nicolas Pitre [this message]
2010-02-24 23:42 ` Junio C Hamano
2010-02-25 0:11 ` Nelson Elhage
2010-02-25 21:39 ` Sverre Rabbelier
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=alpine.LFD.2.00.1002241004010.1946@xanadu.home \
--to=nico@fluxnic.net \
--cc=git@vger.kernel.org \
--cc=junio@pobox.com \
--cc=nelhage@MIT.EDU \
/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).