Stamps

Eduard-Cristian Stefan alexandrul.ct at gmail.com
Mon May 9 14:23:09 CDT 2011


On 2011-05-09 21:06, Kevin Bullock wrote:
> On May 9, 2011, at 1:01 PM, Eduard-Cristian Stefan wrote:
> 
>> On 2011-05-09 20:52, Eduard-Cristian Stefan wrote:
>>> (b) the same stamp can be applied to multiple changesets
>>>    on multiple branches, as in "it works with mercurial 1.8.3+xx"
>>>    (might be very useful, mostly during code refactoring)
>>
>> And the same stamp can be placed on multiple subrepos too,
>> to mark a possible integration point for a full release
> 
> 
> That'd be unnecessary. A stamp on the parent repo is equivalent to a stamp on the parent repo + all subrepos.

I was thinking at the steps before the parent (+ all subrepos) commit:
- given a milestone "A" which targets multiple features, of which not all
might survive to the release
- as each subrepo implements it's part of a feature, it's stamped with "A",
or maybe with multiple "A" stamps (one for each feature implemented)
- the final step would be to choose for each subrepo one of the changesets
stamped with "A" (based on completed features) and commit in the parent repo

The "A" stamp would help in this scenario to filter only the features
implemented in the subrepos and that might be part of the milestone.

Bookmarks can be used for the same purpose, but a single stamp can be used
for multiple branches and multiple changesets in the same subrepo.

Of course, it's a crafted example that should be never encountered
in the  real life :D

Have a nice day,
  Eduard


More information about the Mercurial-devel mailing list