This sounds interesting. Ali
Begin forwarded message: > From: "Peter Arrenbrecht" <[EMAIL PROTECTED]> > Date: August 26, 2008 11:26:31 AM GMT-04:00 > To: mercurial <[EMAIL PROTECTED]> > Subject: RFC: stacks - patch management extension inspired by bzr-loom > Reply-To: [EMAIL PROTECTED] > > Hi all > > I've started work on what I call "stacks": > > http://arrenbrecht.ch/mercurial/stacks.htm > > It's about using hierarchical branching to develop a patch series > collaboratively (as opposed to exchanging versioned mq repos). It is > still quite rudimentary and experimental, but if anyone wants to give > early feedback, I'd welcome it (release early, release often - so > there). > > It's also my first attempt at "literate testing" in the context of > Mercurial (like I believe the hgbook examples work). Currently it > relies on Rextile[1] markup, but if this style of testing is going to > be deemed valuable, I can later switch to whatever markup we shall > agree on. > > From the introduction: > > Stacked patch branches (stacks) is a way to develop a stack of patches > for submission into a main repo. This is for when the main repo does > not want to track the detailed evolution of the patches, so you cannot > use plain branching and merging. But during the patches' development, > you do want to track the detailed evolution and want to collaborate > with team members as naturally as on a normal branch, including > exchange and reviewing of changesets. So stacks allow to develop > patches as basically normal Mercurial branches, which later get thrown > away (or archived) when the patches have been accepted. > > Stacks is thus an alternative for mq. While mq is very useful for > fairly short-lived, single-person patches, I find it lacking for > long-term and/or team efforts. Versioned mq patch queues are hard to > review (diffs of diffs) and merge, and we lack the usual merging > niceness in Mercurial when updating later patches to changes in > earlier ones. > > -parren > > [1]http://arrenbrecht.ch/rextile/ > _______________________________________________ > Mercurial mailing list > [EMAIL PROTECTED] > http://selenic.com/mailman/listinfo/mercurial > _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
