|
|
Chromium Code Reviews|
Created:
3 years, 5 months ago by brucedawson Modified:
3 years, 5 months ago CC:
chromium-reviews Target Ref:
refs/heads/master Project:
chromium Visibility:
Public. |
DescriptionAdd comment warning about modifying landmines
Modifying landmines has greater consequences than is sometimes realized
for developers, especially on Windows. Add a comment to warn editors of
these consequences.
This was inspired by https://chromium-review.googlesource.com/c/544867/
R=dpranke@chromium.org
BUG=736939
Review-Url: https://codereview.chromium.org/2959743004
Cr-Commit-Position: refs/heads/master@{#482639}
Committed: https://chromium.googlesource.com/chromium/src/+/46ac6b742672a82001cd3d8ef0c7525be72a9097
Patch Set 1 #
Messages
Total messages: 16 (9 generated)
The CQ bit was checked by brucedawson@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Does this seem appropriate? We could also assign explicit OWNERS to further discourage landmines. I used to be a serial violator of this rule but I am now reformed.
Description was changed from ========== Add comment warning about modifying landmines Modifying landmines has greater consequences than is sometimes realized for developers, especially on Windows. Add a comment to warn editors of these consequences. This was inspired by https://chromium-review.googlesource.com/c/544867/ R=dpranke@chromium.org ========== to ========== Add comment warning about modifying landmines Modifying landmines has greater consequences than is sometimes realized for developers, especially on Windows. Add a comment to warn editors of these consequences. This was inspired by https://chromium-review.googlesource.com/c/544867/ R=dpranke@chromium.org BUG=736939 ==========
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
I think this looks fine (lgtm) though I don't think it'll matter much. Apart from making them undoable, I'm tempted to say that we should add an "are you sure" presubmit warning or something ...
The CQ bit was checked by brucedawson@chromium.org
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
On 2017/06/27 00:32:21, Dirk Pranke wrote: > I think this looks fine (lgtm) though I don't think it'll matter much. > > Apart from making them undoable, I'm tempted to say that we should add an "are > you sure" presubmit warning or something ... Agreed.
CQ is committing da patch.
Bot data: {"patchset_id": 1, "attempt_start_ts": 1498579251554700, "parent_rev":
"eafc049ccec45550ea86089c463918131d04e927", "commit_rev":
"46ac6b742672a82001cd3d8ef0c7525be72a9097"}
Message was sent while issue was closed.
Description was changed from ========== Add comment warning about modifying landmines Modifying landmines has greater consequences than is sometimes realized for developers, especially on Windows. Add a comment to warn editors of these consequences. This was inspired by https://chromium-review.googlesource.com/c/544867/ R=dpranke@chromium.org BUG=736939 ========== to ========== Add comment warning about modifying landmines Modifying landmines has greater consequences than is sometimes realized for developers, especially on Windows. Add a comment to warn editors of these consequences. This was inspired by https://chromium-review.googlesource.com/c/544867/ R=dpranke@chromium.org BUG=736939 Review-Url: https://codereview.chromium.org/2959743004 Cr-Commit-Position: refs/heads/master@{#482639} Committed: https://chromium.googlesource.com/chromium/src/+/46ac6b742672a82001cd3d8ef0c7... ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1) as https://chromium.googlesource.com/chromium/src/+/46ac6b742672a82001cd3d8ef0c7...
Message was sent while issue was closed.
thakis@chromium.org changed reviewers: + thakis@chromium.org
Message was sent while issue was closed.
Do you think anyone will look at this file? landmines are added to get_landmines.py, which already has a comment like this. I suppose we could copy the comment in get_landmines.py from the top to the bottom too, so it's more in sight. But adding the comment to this file seems unlikely to help.
Message was sent while issue was closed.
On 2017/06/27 16:09:21, Nico (vacation Jun 30-Jul 11) wrote: > Do you think anyone will look at this file? landmines are added to > get_landmines.py, which already has a comment like this. I suppose we could copy > the comment in get_landmines.py from the top to the bottom too, so it's more in > sight. > > But adding the comment to this file seems unlikely to help. Drat. Yep, wrong file. I'll add the warnings to the correct file. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
