Closed
Bug 962327
Opened 10 years ago
Closed 10 years ago
Update when reusing existing bug
Categories
(Developer Services :: Mercurial: bzexport, defect)
Developer Services
Mercurial: bzexport
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sfink, Assigned: sfink)
Details
Attachments
(1 file)
3.27 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
|hg bzexport 12345| should update the top mq patch by default. Right now, it'll only update by default if a new bug is being created. I think I just messed that up.
Assignee | ||
Comment 1•10 years ago
|
||
I think it would all probably work if I just did - update_patch = opts['update'] or opts['new'] + update_patch = opts['new'] or opts['update'] but this all seems much too cryptic, so spelling it out in detail.
Attachment #8363298 -
Flags: review?(josh)
Comment 2•10 years ago
|
||
No, I changed this behavior in: http://hg.mozilla.org/users/tmielczarek_mozilla.com/bzexport/rev/540b04fc2c19 It used to be "only update when you specify --update". I'm fine with it either way, I just figured "put the bug number in the commit message when filing a new bug" was a very inoffensive action. I think "put the bug number in the commit message if there's no bug number already there" is probably similarly inoffensive.
Assignee | ||
Comment 3•10 years ago
|
||
Comment on attachment 8363298 [details] [diff] [review] Update when reusing existing bug (In reply to Ted Mielczarek [:ted.mielczarek] from comment #2) > It used to be "only update when you specify --update". I'm fine with it > either way, I just figured "put the bug number in the commit message when > filing a new bug" was a very inoffensive action. I think "put the bug number > in the commit message if there's no bug number already there" is probably > similarly inoffensive. Aha! You have an opinion, which means you're itching to review. Perfect!
Attachment #8363298 -
Flags: review?(josh) → review?(ted)
Comment 4•10 years ago
|
||
Comment on attachment 8363298 [details] [diff] [review] Update when reusing existing bug Review of attachment 8363298 [details] [diff] [review]: ----------------------------------------------------------------- I think ideally we'd do the right thing by default here and not need the options, but this is fine. ::: __init__.py @@ +1006,5 @@ > + update = True > + elif opts['new']: > + update = ui.configbool("bzexport", "update-patch", True) > + else: > + update = ui.configbool("bzexport", "update-patch", False) This is definitely cleaner.
Attachment #8363298 -
Flags: review?(ted) → review+
Assignee | ||
Comment 5•10 years ago
|
||
http://hg.mozilla.org/users/tmielczarek_mozilla.com/bzexport/rev/3420668a4f37
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Other Applications → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•