From: Nicolas Pitre <nico@fluxnic.net>
To: Stephen Boyd <bebarino@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] git-pack-objects.txt: fix grammatical errors
Date: Sat, 02 Apr 2011 12:03:11 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1104021155230.28032@xanadu.home> (raw)
In-Reply-To: <1301475606-11339-1-git-send-email-bebarino@gmail.com>
On Wed, 30 Mar 2011, Stephen Boyd wrote:
> Signed-off-by: Stephen Boyd <bebarino@gmail.com>
> ---
>
> This paragraph might need even more work. Paint away!
>
> Documentation/git-pack-objects.txt | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/git-pack-objects.txt b/Documentation/git-pack-objects.txt
> index a51071e..442018b 100644
> --- a/Documentation/git-pack-objects.txt
> +++ b/Documentation/git-pack-objects.txt
> @@ -190,9 +190,9 @@ self-contained. Use `git index-pack --fix-thin`
> (see linkgit:git-index-pack[1]) to restore the self-contained property.
>
> --delta-base-offset::
> - A packed archive can express base object of a delta as
> - either 20-byte object name or as an offset in the
> - stream, but older version of git does not understand the
> + A packed archive can express the base object of a delta as
> + either a 20-byte object name or as an offset in the
> + stream, but older versions of git don't understand the
> latter. By default, 'git pack-objects' only uses the
> former format for better compatibility. This option
> allows the command to use the latter format for
This is misleading and not even true anymore if not using pack-objects.
Most people are using either 'git repack' or even 'git gc', and the
default is to use this parameter since commit 22c79eab.
Nicolas
next prev parent reply other threads:[~2011-04-02 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 9:00 [PATCH] git-pack-objects.txt: fix grammatical errors Stephen Boyd
2011-04-02 16:03 ` Nicolas Pitre [this message]
2011-04-02 18:03 ` Junio C Hamano
2011-04-02 21:16 ` Nicolas Pitre
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
List information: http://vger.kernel.org/majordomo-info.html
* 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.1104021155230.28032@xanadu.home \
--to=nico@fluxnic.net \
--cc=bebarino@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).