When investigating (hg log -G, hg bisect, ...) it's common to have a sense of what an interesting commit is, but want to see what's around it (ancestors to some depth, descendants to some depth). We propose to add: around(set, depth) -- which will include all* changesets which are ancestors/descendants of a changeset in set and add an optional argument depth to ancestors(set) and descendants(set) as: ancestors(set[, depth]) -- will include depth levels of ancestors of changesets in set descendants(set[, depth]) -- will include depth levels of descendants of changesets in set ancestors(set, 0) == set descendants(set, 0) == set around(set, 0) == set around(set, 1) = ancestors(set, 1) + descendants(set, 1)
(marked as confirmed since the proposal sounds generally nice.)
Bug was inactive for 150 days, archiving
Reopening because this does sound very nice!
ancestors(set, depth) and descendants(set, depth) will be basic building blocks of set{generation} operator. So I started implementing them. http://markmail.org/message/sjnnwa43s4eksu62 I won't add around() because it can be easily defined as an alias.
Bug was set to IN_PROGRESS for 14 days, moving back to confirmed
Implemented by 272a44cac57e and a53bfc2845f2.
Bug was set to TESTING for 8 days, resolving