Re: `about-emacs' - what about the revno?

[Stefan Monnier <monnier@iro.umontreal.ca>]

>>>> PS: As mentioned earlier, it requires internet access.
>>> I thought bzr is a dVCS?
>> Yes, but we want to relate someone's code to the one in our
>> repository.
> The question here is: are you interested on bug reports coming from
> builds that contains unknown modifications?

Not terribly, but we have handled some such reports in the past (Debian
and a few others come to mind).  And I think we want to encourage people
to develop local patches in their local branches (with the hope they'll
contribute them eventually), as well as encourage people to report bugs,
so yes, I think we are interested.  We usually accept the report, tho we
also often ask people to try and reproduce the bug on a vanilla build.

> (I guess that at some point into the future bug reports for sanctioned
> feature branches will be accepted too.

Actually, that's already the case since we have both the trunk and the
emacs-23 branch (not exactly "feature branches", but the problem is the
same).

> Then, the "common ancestor with trunk" approach will need an overhaul.

It already does.  We want "nick+revno+changes" where "nick" is the name
of one of the branches in our repository and "changes" is some
representation of the changes relative to "nick+revno".  Can be just
a boolean indicating whether there are changes, or it could be something
else like the "bzr diff|wc" I suggested.


        Stefan