From: Michael Witten <mfwitten@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 00/10] Docs: git tag
Date: Tue, 29 Mar 2011 08:59:48 -0500 [thread overview]
Message-ID: <AANLkTi=U8amjCM7=bn2=ewJs2UpNG+D+sCKm4pPf4hP-@mail.gmail.com> (raw)
In-Reply-To: <4D917B5E.1000600@drmicha.warpmail.net>
On Tue, Mar 29, 2011 at 01:25, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> Junio C Hamano venit, vidit, dixit 28.03.2011 20:04:
>> Michael Witten <mfwitten@gmail.com> writes:
>>
>>> Small patches fixing up the `git tag' docs.
>>>
>>> Michael Witten (10):
>>> Docs: git tag: Add `the'
>>> Docs: git tag: peoples back -> people's backs
>>> Docs: git tag: Revise a paragraph.
>>> Docs: git tag: other's -> the other person's
>>> Docs: git tag: Streamline a sentence.
>>> Docs: git tag: Add missing 'the'
>>> Docs: git tag: Use 'who' again
>>> Docs: git tag: Remove superfluous 'with'
>>> Docs: git tag: Use semicolon
>>> Docs: git tag: Rewrite discussion of GIT_COMMITTER_DATE
>>
>> Thanks; all looked sensible changes, except for 7/10 which I somehow find
>> the original is more readable than the new text, partly because the
>> sentences are shorter but more importantly because the two sentences make
>> two separate assertions (the first is about what "one-shot" pull means,
>> the second is about why automatic tag following is not desired in that
>> situation).
>
> Looked mostly sensible to me (and I share Junio's view on 7), too,
> although I probably would have changed "other's" simply to "others'".
I probably chose the singular variant for 2 reasons: I generally
prefer singular renditions, and the sentence is referring to an
example of a pull-request from one individual.
On Tue, Mar 29, 2011 at 01:25, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> Those 10 patches could have been 1 actually, they are really divided
> into atoms (which is not bad per se) even though they all fall under
> "cosmetic language corrections and improvements" without any content
> change nor restructuring.
It's always hard to tell what delineations will be appreciated.
However, it's almost always the case that the smaller a patch is, the
more quickly it can be reviewed and approved (also, the smaller the
diff, the more meaningful the commit message), so I err on the side of
too small; after all, it's generally much easier to squash than to
split.
Of course, I would have no problem if Junio ultimately saw fit to
squash some or all of them (with a note that such squashing has
occurred).
Thanks for your input.
prev parent reply other threads:[~2011-03-29 14:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 15:32 [PATCH 00/10] Docs: git tag Michael Witten
2011-03-28 14:35 ` [PATCH 01/10] Docs: git tag: Add `the' Michael Witten
2011-03-28 14:40 ` [PATCH 02/10] Docs: git tag: peoples back -> people's backs Michael Witten
2011-03-28 18:02 ` Eric Raible
2011-03-29 2:02 ` Michael Witten
2011-03-28 14:49 ` [PATCH 03/10] Docs: git tag: Revise a paragraph Michael Witten
2011-03-28 14:51 ` [PATCH 04/10] Docs: git tag: other's -> the other person's Michael Witten
2011-03-28 14:53 ` [PATCH 05/10] Docs: git tag: Streamline a sentence Michael Witten
2011-03-28 14:55 ` [PATCH 06/10] Docs: git tag: Add missing 'the' Michael Witten
2011-03-28 14:58 ` [PATCH 07/10] Docs: git tag: Use 'who' again Michael Witten
2011-03-28 14:59 ` [PATCH 08/10] Docs: git tag: Remove superfluous 'with' Michael Witten
2011-03-28 15:01 ` [PATCH 09/10] Docs: git tag: Use semicolon Michael Witten
2011-03-28 15:11 ` [PATCH 10/10] Docs: git tag: Rewrite discussion of GIT_COMMITTER_DATE Michael Witten
2011-03-28 18:04 ` [PATCH 00/10] Docs: git tag Junio C Hamano
2011-03-29 2:06 ` Michael Witten
2011-03-29 6:25 ` Michael J Gruber
2011-03-29 13:59 ` Michael Witten [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='AANLkTi=U8amjCM7=bn2=ewJs2UpNG+D+sCKm4pPf4hP-@mail.gmail.com' \
--to=mfwitten@gmail.com \
--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).