All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Thomas Ackermann <th.acker@arcor.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] Add MAINTAINERS file and clarify gui workflows
Date: Mon, 31 Dec 2012 10:32:22 -0800	[thread overview]
Message-ID: <7vlicedqdl.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: loom.20121231T103639-635@post.gmane.org

Thomas Ackermann <th.acker@arcor.de> 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?

Perhaps.  It started as a living document that discusses the state
of affairs as of the time of posting (there are mentions to "the
most recent such release was ...", etc), and because I wanted to
keep it that way (and also I needed somewhere to keep track of it),
I deliberately kept it outside the source tree.

It is an addendum to howto-maintain-git, and what it covers overlaps
with it, so it will need some clean-ups if we want to go the route
you suggest.

Having said all that, I think it is still a good idea to keep the
occasional "A note from he Maintainer" posting on list, and a
version that needs to rever to another document after losing
overlaps with howto-maintain-git will no longer will be suitable
source for it, so...

      parent reply	other threads:[~2012-12-31 18:32 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
2012-12-31 18:32     ` 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=7vlicedqdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.