Hi, Mark Phalan p??e v P? 26. 09. 2008 v 11:11 +0200: > On Fri, 2008-09-26 at 00:25 -0600, Shawn M Emery wrote: > > There seems to be different standards in how changesets are commented > > using mecurial. In specific if there are multiple CRs and multiple > > modules being modified there is a disconnect in the changeset and the > > associated comments. This makes it difficult to correlate specific > > changes in a module to the corresponding CR. Could we have a process > > that requires separate changesets corresponding to individual CR comments? > > Won't this be very difficult with the current situation of per-repo > changesets and thus the requirement to do a "hg reci" before pushing? > > I agree that it would certainly make more sense to have multiple > changesets for multiple CRs. > > -M >
Maybe it should be prohibited to push unrelated CRs in one changeset (and RTI)? It will help with many things, e.g. regression hunting and backports. It isn't so huge problem with Mercurial to move changesets between workspaces if you are working on several CRs in parallel. Today we have some huge-list-CRs changesets in one subsystem which have no reason to go together. Best regards, Milan
