On Thu, Apr 21, 2016 at 01:34:27PM +0200, Eike Rathke wrote: > I think what Richard meant was, to do the changes in a branch of the > public mutt repository instead of your local patch queue so that anyone > can follow/participate/contribute.
Thanks Eike. I think my confusion is because the patches were still under development and at this point still a proposal. Traditionally, we post proposed patches to the list for comment so they can be changed or even entirely scrapped. Once something it pushed up to a clonable Mercurial repository, there is no going back. Branches in Mercurial are different than Git, as they are non-removable. I can understand a large, long-term process of changes going into a "devel" branch (if we had that), but I fully intend to finish this changeset up in the next couple days, and have only been working on these changes since last weekend. However, I admit my knowledge of dvcs development techniques is pretty small. If there is a better way of putting up proposed changes (that can be easily scrapped), please propose it to the list. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA http://www.8t8.us/configs/gpg-key-transition-statement.txt
signature.asc
Description: PGP signature
