From: Raman Gupta <rocketraman@fastmail.fm>
To: Thomas Rast <trast@student.ethz.ch>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCHv2] Update gitworkflows man page to include release workflow
Date: Thu, 12 Nov 2009 11:54:54 -0500 [thread overview]
Message-ID: <4AFC3DDE.7000202@fastmail.fm> (raw)
In-Reply-To: <200911120910.57091.trast@student.ethz.ch>
Thomas Rast wrote:
> Raman Gupta wrote:
>> Junio C Hamano wrote:
>>> Please set the tone straight. If this is to suggest various possible
>>> workflows in general vague terms, "may use" would be good. If this is to
>>> precisely describe what I do, then there won't be "you could do this, or
>>> you could do that." Your "may use" suggests the former, but the commit
>>> log message claims the latter. Which document are you writing?
>> Ok. The current document is inconsistent. In places it uses "the
>> maintainer" and in other places it uses "you". In any case, it seems
>> that the "maintainer" here is not "Junio Hamano" -- rather, it is the
>> reader.
>>
>> Let me create a separate (and first) cleanup patch to fix the existing
>> inconsistencies in this man page. I would prefer to use the pronoun
>> "you" consistently as also suggested by Thomas Rast.
>
> Well, I'm not sure if this is also in reply to my comment
It was mostly, yes.
> } The current gitworkflows is mostly formulated in the imperative, [...]
> } or by directly describing the tools in the third person, [...]
>
> but note that I do not consider the current form to be inconsistent
> (though you may of course convince me otherwise). It addresses the
> presumed user with "you", which is not always the maintainer. For
> example, when talking about patch submission we have
You're right, upon re-reading the original man page I realized it is
consistent.
Thanks,
Raman
next prev parent reply other threads:[~2009-11-12 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 16:08 Update gitworkflows man page to include release workflow rocketraman
2009-11-10 16:08 ` [PATCHv2] " rocketraman
2009-11-10 18:06 ` Štěpán Němec
2009-11-10 18:10 ` Raman Gupta
2009-11-11 13:05 ` Thiago Farina
2009-11-11 15:23 ` Raman Gupta
2009-11-11 19:43 ` Junio C Hamano
2009-11-12 0:32 ` Raman Gupta
2009-11-12 8:03 ` Junio C Hamano
2009-11-12 8:10 ` Thomas Rast
2009-11-12 16:54 ` Raman Gupta [this message]
2009-11-11 20:41 ` Thomas Rast
2009-11-12 8:27 ` 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=4AFC3DDE.7000202@fastmail.fm \
--to=rocketraman@fastmail.fm \
--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).