From: "Michael S. Tsirkin" <mst@redhat.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Add --reference option to git submodule
Date: Tue, 28 Apr 2009 14:27:38 +0300 [thread overview]
Message-ID: <20090428112738.GC27513@redhat.com> (raw)
In-Reply-To: <49F6E419.1020308@drmicha.warpmail.net>
On Tue, Apr 28, 2009 at 01:10:17PM +0200, Michael J Gruber wrote:
> > @@ -177,6 +179,14 @@ OPTIONS
> > This option is only valid for the update command.
> > Don't fetch new objects from the remote site.
> >
> > +--reference <repository>::
> > + This option is only valid for add and update commands. These
>
> This option applies only to add...
The rest of the documentation has 'is only valid' language.
I guess we need to be consistent? Rewrite these as well?
--
MST
prev parent reply other threads:[~2009-04-28 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 6:52 [PATCH] Add --reference option to git submodule Michael S. Tsirkin
2009-04-28 11:10 ` Michael J Gruber
2009-04-28 11:25 ` Michael S. Tsirkin
2009-04-28 13:12 ` Michael J Gruber
2009-04-28 11:27 ` Michael S. Tsirkin [this message]
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=20090428112738.GC27513@redhat.com \
--to=mst@redhat.com \
--cc=git@drmicha.warpmail.net \
--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).