From: Brock Peabody <brock.peabody@gmail.com>
To: git@vger.kernel.org
Subject: Re: help with distributed workflow/signoff
Date: Wed, 14 Jul 2010 17:49:42 +0000 (UTC) [thread overview]
Message-ID: <loom.20100714T193832-914@post.gmane.org> (raw)
In-Reply-To: 20100714171614.GA2799@burratino
Hi Jonathan,
Thanks for your quick, informative response. This is the information I was
hoping to get - how the tool is used by its primary audience. It's going to
take me a while to fully absorb it, but I suspect (as Avery points out in his
reply) that this type of workflow is less workable when there are fewer
reviewers and more patches, most of which are accepted as-is.
Nevertheless, I want to make sure that we keep in mind the way the tool is meant
to be used when choosing our new workflow, rather than trying to force it into a
mold inspired by svn. It would probably do us no harm to be forced to have
fewer, more well considered patches.
Cheers,
Brock
next prev parent reply other threads:[~2010-07-14 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 16:33 help with distributed workflow/signoff Brock Peabody
2010-07-14 17:16 ` Jonathan Nieder
2010-07-14 17:49 ` Brock Peabody [this message]
2010-07-14 17:24 ` Avery Pennarun
2010-07-14 18:06 ` Brock Peabody
2010-07-14 21:03 ` Ævar Arnfjörð Bjarmason
2010-07-14 21:46 ` Brock Peabody
2010-07-14 23:20 ` A Large Angry SCM
2010-07-15 17:42 ` Brock Peabody
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=loom.20100714T193832-914@post.gmane.org \
--to=brock.peabody@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.
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).