Recent Features
| |||||||||||||
KS2008: Development toolsKS2008: Development toolsPosted Sep 17, 2008 0:45 UTC (Wed) by jamesh (guest, #1159)In reply to: KS2008: Development tools by johill Parent article: KS2008: Development tools
To do that kind of thing, people need to be sending more than just plain patches. The equivalent tool that was built to help develop Bazaar is Bundle Buggy. While it can handle plain patches to some extent, it really shines when people send Bazaar bundles which package up all the branch history not present in the target branch. This means that a developer can merge the branch and pull in all of its history. When this is done, it is trivial to detect when a patch has been merged and remove it from the pending list. If someone posts an updated version of a patch, Bundle Buggy can unambiguously tell that it is derived from a previous patch and mark the old one as obsolete. The upshot is that the pending list is a fairly accurate representation of what work needs to be merged whether the developers use the web UI or not.
(Log in to post comments)
KS2008: Development tools Posted Sep 18, 2008 12:13 UTC (Thu) by johill (subscriber, #25196) [Link]
Yes, if you can enforce that kind of thing that works well. However, it doesn't really work well in a distributed setting where the users may not all be using the tool itself.
I'm thinking that something as simple as "quilt mail", the git equivalent or whatever should work just fine when everybody adds the right references header etc.
Of course, I'd need to do more thinking, at which point I could probably write a preliminary version of the tool I'm imagining.
|
|||||||||||||