git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/3] git-bundle.txt: Cleanup
Date: Mon, 23 Aug 2010 14:20:13 +0200	[thread overview]
Message-ID: <4C72677D.9030205@drmicha.warpmail.net> (raw)
In-Reply-To: <201008231359.00417.trast@student.ethz.ch>

Thomas Rast venit, vidit, dixit 23.08.2010 13:59:
> Michael J Gruber wrote:
>> Cleanup various spellings of the same argument
> [...]
>> -       'git rev-list' arguments to define the bundle contents.
>> +       'git-rev-list-args' arguments to define the bundle contents.
> 
> As indicated by the Cc but not the text, this was fallout from my
> automated replacements in 0b444cd (Documentation: spell 'git cmd'
> without dash throughout, 2010-01-10).

No blame intended (and no "git blame" run). I cc'ed you as the doc
sheriff ;)

The change above was really about using the place holder name
consistently, which includes keeping the "-args".

> An analogous change to one of your {tilde} replacements is already in
> Jonathan's series.  The rest probably don't hurt, if only to drive

I was behind an idiotic firewall for the last 2 weeks which not only
blocked vpn and nntp but made it impossible to get larger chunks over
git:, git+ssh: or even scp (bundle) even though bandwidth was no
apparent issue. One of those countries which are currently argueing with
RIM. Makes you wonder how routinely they do content sniffing and how
they react to any (false) triggers. Might also have been an overly eager
institution, of course.

So I didn't see Jonathan's series in time.

> people towards a more consistent {tilde} spelling in the future.

I did some experimenting after noticing that I had many broken ~ (either
disappearing or appearing with spurious \ in the html). I might even
have come up with a rule, but I'm afraid these things change from
asciidoc version to asciidoc version, so that I went the chatty {tilde}.

Cheers (back on home soil),
Michael

  reply	other threads:[~2010-08-23 12:20 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 [this message]
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

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=4C72677D.9030205@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=trast@student.ethz.ch \
    /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).