From: "Štěpán Němec" <stepnem@gmail.com>
To: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 1/1] Random documentation spelling fixes
Date: Fri, 22 Jan 2010 09:36:14 +0100 [thread overview]
Message-ID: <20100122083614.GE7370@headley> (raw)
In-Reply-To: <1264126491-8273-2-git-send-email-vonbrand@inf.utfsm.cl>
Cool!
On Thu, Jan 21, 2010 at 11:14:51PM -0300, Horst H. von Brand wrote:
>
> * "git fast-export" did not export octopus merges correctly.
> diff --git a/Documentation/RelNotes-1.5.6.txt b/Documentation/RelNotes-1.5.6.txt
> index e143d8d..0614225 100644
> --- a/Documentation/RelNotes-1.5.6.txt
> +++ b/Documentation/RelNotes-1.5.6.txt
> @@ -25,7 +25,7 @@ Updates since v1.5.5
> * Many freestanding documentation pages have been converted and made
> available to "git help" (aka "man git<something>") as section 7 of
> the manual pages. This means bookmarks to some HTML documentation
> - files may need to be updated (eg "tutorial.html" became
> + files may need to be updated (eg, "tutorial.html" became
> "gittutorial.html").
What about "e.g.", when you're at it? (And I don't think the comma is
necessary -- and you didn't add it in the very first hunk of the patch
anyway).
> diff --git a/Documentation/git-bisect-lk2009.txt b/Documentation/git-bisect-lk2009.txt
> index 6b7b2e5..eb35f2f 100644
> --- a/Documentation/git-bisect-lk2009.txt
> +++ b/Documentation/git-bisect-lk2009.txt
> @@ -1320,7 +1320,7 @@ So git bisect is unconditional goodness - and feel free to quote that
> ;-)
> _____________
>
> -Acknowledgements
> +Acknowledgments
> ----------------
Both are correct, AFAIK.
Regards,
Štěpán
next prev parent reply other threads:[~2010-01-22 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 2:14 (unknown), Horst H. von Brand
2010-01-22 2:14 ` [PATCH 1/1] Random documentation spelling fixes Horst H. von Brand
2010-01-22 8:36 ` Štěpán Němec [this message]
2010-01-22 9:18 ` Michael J Gruber
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=20100122083614.GE7370@headley \
--to=stepnem@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vonbrand@inf.utfsm.cl \
/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).