From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Thomas Ackermann <th.acker@arcor.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technical
Date: Sun, 30 Dec 2012 17:22:45 +0530 [thread overview]
Message-ID: <CALkWK0=FFt2qfrUop9kwDVQ1FfPm+4WY8kBBY+rtyp16QFOR_A@mail.gmail.com> (raw)
In-Reply-To: <1023165134.213650.1356863340563.JavaMail.ngmail@webmail06.arcor-online.net>
Thomas Ackermann wrote:
> CodingGuidelines and SubmittingPatches are IMHO a little bit hidden in ./Documentation
> and with respect to their content should be better placed in ./Documentation/technical.
I don't think SubmittingPatches and CodingGuidelines belong to
Documentation/technical; that location is mostly reserved for API
documentation. Also, being prominent documents, they're probably
linked to by many places on the internet. I wouldn't want to
unnecessarily break those links.
Ram
prev parent reply other threads:[~2012-12-30 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 10:29 [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technical Thomas Ackermann
2012-12-30 10:31 ` [PATCH 1/3] Move CodingGuidelines to ./technical/coding-guidelines.txt and SubmittingPatches to ./technical/submitting-patches.txt Thomas Ackermann
2012-12-30 10:33 ` [PATCH 2/3] Add coding-guidelines.txt and submitting-patches.txt to ./Documentation/Makefile Thomas Ackermann
2012-12-30 10:35 ` [PATCH 3/3] Convert coding-guidelines.txt and submitting-patches.txt to asciidoc Thomas Ackermann
2012-12-30 11:52 ` Ramkumar Ramachandra [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='CALkWK0=FFt2qfrUop9kwDVQ1FfPm+4WY8kBBY+rtyp16QFOR_A@mail.gmail.com' \
--to=artagnon@gmail.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.
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).