From: Jason Holden <jason.k.holden.swdev@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 0/2] Add MAINTAINERS file and clarify gui workflows
Date: Mon, 31 Dec 2012 13:22:29 -0500 [thread overview]
Message-ID: <20121231182229.GA8665@gmail.com> (raw)
In-Reply-To: <loom.20121231T103639-635@post.gmane.org>
On Mon, Dec 31, 2012 at 09:40:19AM +0000, Thomas Ackermann wrote:
> Junio C Hamano <gitster <at> pobox.com> writes:
>
> >
> > Thanks; I just realized that nothing in Documentation/ hierarchy
> > mentions these; they are only mentioned in "A Note from the
> > Maintainer" I send out every once in a while (kept in MaintNotes of
> > 'todo' branch):
> >
>
> Wouldn't it be a good idea to put MaintNotes somewhere below ./Documentation?
>
> ---
> Thomas
Putting it in Documentation/ would add one more outlier file (Along w/
SubmittingPatches and CodingGuidelines). Documentation/technical seems
too deep. I've got a patch that incorporates the content into the
existing README, but that seems a bit out of place, as the previous content of
README was primarily pointers to other docs.
What about a README.developers at the toplevel?
next prev parent reply other threads:[~2012-12-31 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 18:18 [PATCH 0/2] Add MAINTAINERS file and clarify gui workflows Jason Holden
2012-12-30 18:18 ` [PATCH 1/2] Add top-level maintainers file with email/canonical repository information Jason Holden
2012-12-30 18:18 ` [PATCH 2/2] Provide better guidance for submitting patches against git-gui, gitk Jason Holden
2012-12-30 20:26 ` [PATCH 0/2] Add MAINTAINERS file and clarify gui workflows Junio C Hamano
2012-12-31 9:40 ` Thomas Ackermann
2012-12-31 18:22 ` Jason Holden [this message]
2012-12-31 18:32 ` Junio C Hamano
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=20121231182229.GA8665@gmail.com \
--to=jason.k.holden.swdev@gmail.com \
--cc=git@vger.kernel.org \
/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).