From: Jeff King <peff@peff.net>
To: layer <layer@known.net>
Cc: git@vger.kernel.org
Subject: Re: the workflow (from your POV) of managing git
Date: Mon, 1 Feb 2010 00:46:47 -0500 [thread overview]
Message-ID: <20100201054647.GA7946@coredump.intra.peff.net> (raw)
In-Reply-To: <20375.1265000441@relay.known.net>
On Sun, Jan 31, 2010 at 09:00:41PM -0800, layer wrote:
> Have you written anything up that tells people how you manage the git
> project? Something that could be used by other project leaders? I've
> been googling and haven't been able to find anything other than
> documents which describe the process from the other side (people
> submitting patches).
Try Documentation/howto/maintain-git.txt.
> could learn from by seeing a document on the process you use. For
> example, do you have a script that generates the "what's cooking
> in..." emails?
Check out the 'todo' branch in git.git.
-Peff
prev parent reply other threads:[~2010-02-01 5:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 5:00 the workflow (from your POV) of managing git layer
2010-02-01 5:46 ` Jeff King [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=20100201054647.GA7946@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=layer@known.net \
/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;
as well as URLs for NNTP newsgroup(s).