From: Thomas Ackermann <th.acker@arcor.de>
To: gitster@pobox.com, th.acker@arcor.de
Cc: git@vger.kernel.org
Subject: Aw: Re: [PATCH] Move api-command.txt to the end of API list in api-index.txt
Date: Mon, 17 Dec 2012 10:43:52 +0100 (CET) [thread overview]
Message-ID: <1944303.2385893.1355737432979.JavaMail.ngmail@webmail11.arcor-online.net> (raw)
In-Reply-To: <7vwqwhpy0a.fsf@alter.siamese.dyndns.org>
OK; I would also prefer to have it in ./howto.
So please drop this patch; I will provide a new one.
----- Original Nachricht ----
Von: Junio C Hamano <gitster@pobox.com>
An: Thomas Ackermann <th.acker@arcor.de>
Datum: 16.12.2012 21:01
Betreff: Re: [PATCH] Move api-command.txt to the end of API list in
api-index.txt
> Thomas Ackermann <th.acker@arcor.de> writes:
>
> > - because it describes a different form of API than the other api-*
> documents
>
> It makes me wonder if a more correct "fix" is to move this document
> to the ../howto/ hierarchy.
>
---
Thomas
prev parent reply other threads:[~2012-12-17 9:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1582223824.296627.1355560147565.JavaMail.ngmail@webmail08.arcor-online.net>
[not found] ` <1479174763.154268.1350408444997.JavaMail.ngmail@webmail15.arcor-online.net>
2012-10-16 17:17 ` [Patch v3 0/8] Create single PDF for all HTML files Thomas Ackermann
2012-10-16 17:20 ` [Patch v3 1/8] Split over-long synopsis in git-fetch-pack.txt into several lines Thomas Ackermann
2012-10-16 17:21 ` [Patch v3 2/8] Shorten two over-long lines in git-bisect-lk2009.txt by abbreviating some sha1 Thomas Ackermann
2012-10-16 17:23 ` [Patch v3 3/8] Change headline of technical/send-pack-pipeline.txt to not confuse its content with content from git-send-pack.txt Thomas Ackermann
2012-10-16 17:24 ` [Patch v3 4/8] Prerequisites for creating nice html for all files in Documentation/technical Thomas Ackermann
2012-10-16 17:25 ` [Patch v3 5/8] Prerequisites for creating nice html for all files in Documentation/howto Thomas Ackermann
2012-10-16 17:26 ` [Patch v3 6/8] Prerequisites for creating nice html for all files in Documentation/RelNotes Thomas Ackermann
2012-10-16 17:27 ` [Patch v3 7/8] Create pdf from all html files Thomas Ackermann
2012-10-16 17:28 ` [Patch v3 8/8] Wire everything into Makefile and Documentation/Makefile Thomas Ackermann
2012-10-16 22:11 ` [Patch v3 0/8] Create single PDF for all HTML files Junio C Hamano
2012-12-15 8:29 ` [Patch] Renumber list in api-command.txt Thomas Ackermann
2012-12-16 8:42 ` [PATCH] Remove misleading date form api-index-skel.txt Thomas Ackermann
2012-12-16 8:47 ` Andreas Schwab
2012-12-16 19:59 ` Junio C Hamano
2012-12-16 12:23 ` [PATCH] Move api-command.txt to the end of API list in api-index.txt Thomas Ackermann
2012-12-16 20:01 ` Junio C Hamano
2012-12-17 9:43 ` Thomas Ackermann [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1944303.2385893.1355737432979.JavaMail.ngmail@webmail11.arcor-online.net \
--to=th.acker@arcor.de \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).