From: layer <layer@known.net>
To: git@vger.kernel.org
Subject: the workflow (from your POV) of managing git
Date: Sun, 31 Jan 2010 21:00:41 -0800 [thread overview]
Message-ID: <20375.1265000441@relay.known.net> (raw)
Junio, greetings.
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).
A lot can be gleaned by looking at it from the patch-submitter side,
but I'm guessing there are lots of little tips that project leads
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?
Thanks!
Kevin
next reply other threads:[~2010-02-01 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 5:00 layer [this message]
2010-02-01 5:46 ` the workflow (from your POV) of managing git Jeff King
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=20375.1265000441@relay.known.net \
--to=layer@known.net \
--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.
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.