mercurial/crew at 24396: 5 outgoing changesets

[Pierre-Yves David]

On 01/19/2015 06:31 AM, Thomas Arendsen Hein wrote:
> * Sean Farley <sean.michael.farley at gmail.com> [20150118 17:57]:
>> Mercurial Commits writes:
>>
>>> 5 outgoing changesets in mercurial/crew:
>>
>> These have already been obsoleted. As a stopgap, can a crew member pull
>> from mpm and push to crew?
>
> Someone already did this.
>
>> In the future, can these emails get smarter
>> about obsolescence markers?
>
> Good idea, I just switched to using the crew+main repo for these
> mails, so obsolescence should now be taken into account.
> Please mail again to hg at intevation.org if not.
>
> But I somehow feel that "hg outgoing" should not report these
> changes as outgoing or that there should be a way to check this via
> revsets, but I don't know how complicated the implementation for
> this would be. Ideas?

The discovery need to be extended with a concept of "I've heard about 
this node, it is obsoleted by some known node on my end.

>
> Regards,
> Thomas
>

-- 
Pierre-Yves David