[Pkg-puppet-devel] Commit practices, code review, etc

[Stig Sandbeck Mathisen]

Andrew Pollock <apollock at debian.org> writes:

> A lightweight start would be to start emailing patches around instead
> of committing them first, perhaps.

That would make the workflow something like this:

git checkout -b bts/<bugnumber> master
<hack>
git commit -m 'useful changelog entry'
git format-patch <options> master

<comments on the mailing list>

Then the patch is merged with "git merge" by the submitter, or with "git
am" by someone else, and pushed to master on alioth.

-- 
Stig Sandbeck Mathisen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20100218/b63ecd65/attachment.pgp>