From: Thomas Rast <trast@student.ethz.ch>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 3/3] git-bundle.txt: Clarify rev-list-args restrictions
Date: Mon, 23 Aug 2010 14:01:25 +0200 [thread overview]
Message-ID: <201008231401.26329.trast@student.ethz.ch> (raw)
In-Reply-To: <4a2d0ecb46d274f6143caab6982535bfb678d10e.1282553586.git.git@drmicha.warpmail.net>
Michael J Gruber wrote:
> diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt
> index 3cdbc72..38e59af 100644
> --- a/Documentation/git-bundle.txt
> +++ b/Documentation/git-bundle.txt
> @@ -59,7 +59,8 @@ unbundle <file>::
>
> <git-rev-list-args>::
> A list of arguments, acceptable to 'git rev-parse' and
> - 'git rev-list', that specifies the specific objects and references
> + 'git rev-list' (and containg a named ref, see SPECIFYING REFERENCES
> + below), that specifies the specific objects and references
> to transport. For example, `master{tilde}10..master` causes the
> current master reference to be packaged along with all objects
> added since its 10th ancestor commit. There is no explicit
Ack on this, too; having it point at "Specifying References" is a good
thing.
--
Thomas Rast
trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2010-08-23 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 9:02 [PATCH 0/3] git-bundle.txt options clarification Michael J Gruber
2010-08-23 9:02 ` [PATCH 1/3] git-bundle.txt: Cleanup Michael J Gruber
2010-08-23 11:59 ` Thomas Rast
2010-08-23 12:20 ` Michael J Gruber
2010-08-23 9:02 ` [PATCH 2/3] git-bundle.txt: whitespace cleanup Michael J Gruber
2010-08-23 9:02 ` [PATCH 3/3] git-bundle.txt: Clarify rev-list-args restrictions Michael J Gruber
2010-08-23 12:01 ` Thomas Rast [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=201008231401.26329.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--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).