Bug 29718 - mark-bug-fixed: add -u|--update-only switch
Summary: mark-bug-fixed: add -u|--update-only switch
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-24 10:31 PDT by David Kilzer (:ddkilzer)
Modified: 2009-09-25 15:03 PDT (History)
2 users (show)

See Also:


Attachments
Patch v1 (2.21 KB, patch)
2009-09-24 10:31 PDT, David Kilzer (:ddkilzer)
eric: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description David Kilzer (:ddkilzer) 2009-09-24 10:31:35 PDT
Created attachment 40072 [details]
Patch v1

Reviewed by NOBODY (OOPS!).

* Scripts/mark-bug-fixed:
(MarkBugFixed.__init__): Added -u|--update-only switch to list
of parse options.
(MarkBugFixed.main): When -u|--update-only is specified, add a
comment to the bug without marking it Resolved/Fixed.
---
 2 files changed, 19 insertions(+), 2 deletions(-)
Comment 1 Eric Seidel (no email) 2009-09-24 11:05:06 PDT
I think this is kinda a strange command-line API (calling mark-as-fixed but not having it mark anything as fixed), but I like the functionality.  An Apple person would have to comment as to if this makes sense for y'alls workflow.
Comment 2 David Kilzer (:ddkilzer) 2009-09-25 12:52:57 PDT
(In reply to comment #1)
> I think this is kinda a strange command-line API (calling mark-as-fixed but not
> having it mark anything as fixed), but I like the functionality.  An Apple
> person would have to comment as to if this makes sense for y'alls workflow.

This is useful if you have more than one patch that is required to fix a bug, but don't want to close the bug after the first commit.

Some folks like to commit fixes to individual directories separately (one for WebCore, one for LayoutTests), which makes this flag useful as well.
Comment 3 David Kilzer (:ddkilzer) 2009-09-25 13:02:08 PDT
(In reply to comment #2)
> This is useful if you have more than one patch that is required to fix a bug,
> but don't want to close the bug after the first commit.

I don't see why creating a second script would be helpful in this case.  (The most common workflow is to mark the bug as fixed, but you use the same script to update it as well.)

Do you have another suggestion for the script's name?  I did not want to use "update-bug" since there are too many update-* scripts already.  :)

> Some folks like to commit fixes to individual directories separately (one for
> WebCore, one for LayoutTests), which makes this flag useful as well.

BTW, I don't condone this workflow.
Comment 4 Eric Seidel (no email) 2009-09-25 13:42:13 PDT
Comment on attachment 40072 [details]
Patch v1

OK.  You might want to make clear in the -u help that it will add the fixed revision to the bug as well, not just the comment you pass in -m.  I think that was my initial confusion is that I thought you had effectively created a "add-comment" command, but now I see that this is still really a "mark-bug-with-revision" behavior even if it doesn't always close the bug.
Comment 5 David Kilzer (:ddkilzer) 2009-09-25 15:03:31 PDT
Committed r48772: <http://trac.webkit.org/changeset/48772>