I agree with Gavin this makes reading a bug much simpler when it comes to understanding where a patch has landed especially when backouts occur. The information is added for other readers of the bug not the developer of the patch.
Kevin Brosnan On Mon, Oct 8, 2012 at 5:56 AM, Gavin Sharp <ga...@gavinsharp.com> wrote: > I disagree. "Pushed to inbound" is an important status to have > indicated in the bug, and the best way to do that is to include the > inbound changeset URL (even though it will be the same revision when > it gets to m-c, it's useful to know where it is until it gets there). > It also helps with backouts, and for later identifying the progression > of a patch. > > Gavin > > On Mon, Oct 8, 2012 at 11:03 AM, Nicholas Nethercote > <n.netherc...@gmail.com> wrote: >> Hi, >> >> In https://wiki.mozilla.org/Tree_Rules/Inbound, one of the steps under >> "Please do the following after pushing to inbound" is: >> >> "Add the inbound changeset URL to the bug. If there are multiple >> patches on the bug and you are not pushing all of them, please >> indicate which one(s) you pushed (eg: use patch -> details -> comment >> on patch, or else use the new per-patch checkin+ flags)." >> >> I heard someone say today that this should be an optional step. I >> think the rationale is that it's unnecessary because the subsequent >> mozilla-central links usually contain much the same information. I am >> wondering if others agreed or disagreed with this opinion. >> >> Thanks. >> >> Nick >> _______________________________________________ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
