git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Jim Meyering <jim@meyering.net>
Cc: Junio C Hamano <gitster@pobox.com>, git list <git@vger.kernel.org>
Subject: Re: [PATCH] fix many comment typos
Date: Sun, 03 Jun 2012 13:44:10 +0200	[thread overview]
Message-ID: <4FCB4E0A.5080107@lsrfire.ath.cx> (raw)
In-Reply-To: <87396ceuoy.fsf@rho.meyering.net>

Am 03.06.2012 09:11, schrieb Jim Meyering:
> Perhaps a more palatable change, here and in the other two places:
> s/seeked/cg-seek'd/, i.e.,
>
> - * "git bisect" showed mysterious "won't bisect on seeked tree" error message.
> + * "git bisect" showed mysterious "won't bisect on cg-seek'd tree" error message.
>
> Then, if someone does this again, it will be more obvious that
> it is not a typo.

This change is only valid if the command "git bisect" at some point 
printed "won't bisect on cg-seek'd tree" instead of "won't bisect on 
seeked tree".  And even then, it doesn't make now sense to change 
already published release notes (Documentation/RelNotes/1.5.4.4.txt), 
after the fact.

René

  reply	other threads:[~2012-06-03 11:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-02  8:03 [PATCH] fix many comment typos Jim Meyering
2012-06-02 23:01 ` Junio C Hamano
2012-06-02 23:47   ` Hilco Wijbenga
2012-06-03  0:46     ` Junio C Hamano
2012-06-03  2:39       ` Hilco Wijbenga
2012-06-03  7:11   ` Jim Meyering
2012-06-03 11:44     ` René Scharfe [this message]
2012-06-03 12:58       ` Jim Meyering
2012-06-03 21:31         ` Junio C Hamano
2012-06-03 21:30       ` Junio C Hamano

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=4FCB4E0A.5080107@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jim@meyering.net \
    /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).