Merge incorrectly reported on crbug

11 views
Skip to first unread message

François Doray

unread,
Sep 8, 2016, 1:43:39 PM9/8/16
to chromi...@chromium.org
This morning I landed a change https://codereview.chromium.org/2319623002/ It was correctly reported on the associated crbug https://bugs.chromium.org/p/chromium/issues/detail?id=622400#c18 However, a few hours later, a merge to 2854 (the current branch) was unexpectedly reported https://bugs.chromium.org/p/chromium/issues/detail?id=622400#c19

It seems that many commits have been incorrectly reported as merges to 2854 https://bugs.chromium.org/p/chromium/issues/list?q=label:merge-merged-2854

Michael Moss

unread,
Sep 8, 2016, 1:47:19 PM9/8/16
to fdo...@chromium.org, chromium-dev
That's fallout from cleanup of a bad release branching operation last night. Nothing was incorrectly merged to 2854.

On Thu, Sep 8, 2016 at 10:42 AM, François Doray <fdo...@chromium.org> wrote:
This morning I landed a change https://codereview.chromium.org/2319623002/ It was correctly reported on the associated crbug https://bugs.chromium.org/p/chromium/issues/detail?id=622400#c18 However, a few hours later, a merge to 2854 (the current branch) was unexpectedly reported https://bugs.chromium.org/p/chromium/issues/detail?id=622400#c19

It seems that many commits have been incorrectly reported as merges to 2854 https://bugs.chromium.org/p/chromium/issues/list?q=label:merge-merged-2854

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

Reply all
Reply to author
Forward
0 new messages