Christian Robottom Reis wrote: > On Wed, Oct 03, 2007 at 05:54:58PM +0200, Sebastien Bacher wrote: >> Le mercredi 03 octobre 2007 à 12:38 -0300, Christian Robottom Reis a >> écrit : >> >>> Sure. But how do you find out, in Launchpad, that this happened? Only by >>> browsing an upstream code import, I guess. Could we do something in the >>> UI to make this easier to get to? >> I'm not sure to understand the question. Having the maintainer marking >> the bug Fix Commited with a comment saying that the bug has been fixed >> upstream should be enough information > > That's not /really/ what Fix Committed is meant to be used for (see my > other posts regarding RCS support), but for now, it'll do. > > I'll explain my question more broadly. Let's say there is a bug reported > against Ubuntu eog. Now we know that eog is actually packaged from > > https://edge.launchpad.net/eog > > Becase of: > > https://edge.launchpad.net/eog/+distributions > > We also have a code import of EOG: > > https://code.edge.launchpad.net/~vcs-imports/eog/head > > (Yeah, it's stopped but I'm fixing the RCS details to get it to restart. > Imagine it's running normally just to help me out.) > > It would be pretty cool if you could actually peek at the EOG RCS log > and see "ah, they fixed this bug upstream already". I'm not sure what UI > we'd offer for this, which is why I was asking. This sounds interesting. Maybe you could add a link in the Actions portlet or where you think it suites best to the trunk log, being the log an html page where the revision numbers are links to the revision's diff.
Attachment:
signature.asc
Description: OpenPGP digital signature
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)