New issue
Advanced search Search tips

Issue 792970 link

Starred by 1 user
Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 614164



Sign in to add a comment

use a better description in merge-applying merge commits

Project Member Reported by akes...@chromium.org, Dec 7 2017 
The recently landed kernel merge commit https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/790763 produced a history like this:

*   aa459d7d840f9 Merge commit 'b4da0a97e9cdb5beeac74bbbc27b2699840812b1' into patch_branch
|\  
| *   b4da0a97e9cdb CHROMIUM: Merge tag 'v4.4.104' into chromeos-4.4
| |\  
| | * bd37993918224 (tag: v4.4.104, cros/linux/v4.4.104) Linux 4.4.104
| | * bd249dd078272 nfsd: Fix another OPEN stateid race
| | * 54298082dbacb nfsd: Fix stateid races between OPEN and CLOSE
| | * d7f5f10f5159f nfsd: Make init_open_stateid() a bit more whole
.
.
.


The topology is fine, but the description "Merge commit 'b4da0a97e9cdb5beeac74bbbc27b2699840812b1' into patch_branch" is unenlightening. This should be something like "Apply merge commit XXX into working branch" or something

Comment 1 by akes...@chromium.org, Dec 7 2017

Blocking: 614164

Comment 2 by akes...@chromium.org, Dec 20 2017

Labels: -Pri-2 Hotlist-Fixit Pri-3
Owner: ----
Status: Available (was: Assigned)
Project Member

Comment 3 by sheriffbot@chromium.org, Dec 21

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment