Monotone for Patch Writers

[Richard Laager]

We should come up with a simple tutorial or something on Monotone for
patch writers, specifically addressing issues such as branching.

From the reading I've done see [1] and the rest of the thread, it seems
a good way to deal with this might be:

Contributors use a branch locally and propagate changes from trunk. Then
they send in a patch, which the patch acceptor would commit as-is using
--author to specify the actual author of the patch. Then, he'd make
changes if necessary, commit those, then push.

Richard

[1]
http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-January/001189.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://pidgin.im/pipermail/devel/attachments/20070410/17762285/attachment.sig>