From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Frank Sorenson <frank@tuxrocks.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-repack-script: Add option to repack all objects.
Date: Mon, 29 Aug 2005 14:57:46 -0400 [thread overview]
Message-ID: <43135AAA.4070406@gmail.com> (raw)
In-Reply-To: <7v3bosbn1o.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> A Large Angry SCM <gitzilla@gmail.com> writes:
>
>>Frank,
>>
>>Can you produce a patch to update the git-repack-script documentation to
>>reflect the new functionality?
>
> Not including the doc changes in the patch was my fault, but the
> message was meant primarily as an explanation of what I meant,
> not for immediate inclusion in the master branch.
>
> I have some other documentation updates sitting in the proposed
> updates, so I'd do it myself along with other manual pages if
> you and Frank do not mind.
>
> In any case, I first would like to make sure that the proposed
> patch you are replying to is something Frank agrees to.
>
I sent my request to Frank because he was/is the sponsor of the change
but anyone can provide the documentation. :-)
I think it'd be a good idea for documentation updates to accompany all
patches (and for the maintainer to not be shy about asking for them).
Just my $0.02 as I look at which commands have no documentation.
next prev parent reply other threads:[~2005-08-29 18:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 8:41 [PATCH] git-repack-script: Add option to repack all objects Frank Sorenson
2005-08-28 21:06 ` Junio C Hamano
2005-08-29 7:41 ` Frank Sorenson
2005-08-29 16:48 ` Junio C Hamano
2005-08-29 17:34 ` Junio C Hamano
2005-08-29 18:29 ` A Large Angry SCM
2005-08-29 18:44 ` Junio C Hamano
2005-08-29 18:57 ` A Large Angry SCM [this message]
2005-08-29 19:44 ` Junio C Hamano
2005-08-29 18:59 ` Frank Sorenson
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=43135AAA.4070406@gmail.com \
--to=gitzilla@gmail.com \
--cc=frank@tuxrocks.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).