From: Junio C Hamano <gitster@pobox.com>
To: Thomas Ackermann <th.acker@arcor.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/3] Move api-command.txt from ./technical/ to ./howto
Date: Fri, 21 Dec 2012 10:33:58 -0800 [thread overview]
Message-ID: <7v38yz1ch5.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1595193006.286662.1356112971883.JavaMail.ngmail@webmail14.arcor-online.net> (Thomas Ackermann's message of "Fri, 21 Dec 2012 19:02:51 +0100 (CET)")
Thomas Ackermann <th.acker@arcor.de> writes:
> "api-command.txt" describes a different kind of API than the other api-* documents.
> So better move it to the howto documents in ./Documentation/howto and rename
> to "new-command.txt".
>
> [PATCH 1/3] Move ./technical/api-command.txt to ./howto/new-command.txt
> [PATCH 2/3] Add new-command.txt to ./Documentation/Makefile
> [PATCH 3/3] Amend new-command.txt to be processed correctly by howto-index.sh
>
> Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
Seems good from a cursory look, but I think this is better done in a
single patch. If you do not mind, I'll squash them into one.
Thanks.
prev parent reply other threads:[~2012-12-21 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 18:02 [PATCH 0/3] Move api-command.txt from ./technical/ to ./howto Thomas Ackermann
2012-12-21 18:05 ` [PATCH 1/3] Move ./technical/api-command.txt to ./howto/new-command.txt Thomas Ackermann
2012-12-21 18:06 ` [PATCH 2/3] Add new-command.txt to ./Documentation/Makefile Thomas Ackermann
2012-12-21 18:07 ` [PATCH 3/3] Amend new-command.txt to be processed correctly by howto-index.sh Thomas Ackermann
2012-12-21 18:33 ` Junio C Hamano [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=7v38yz1ch5.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=th.acker@arcor.de \
/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