Closed Bug 728778 Opened 12 years ago Closed 11 years ago

Add feedback flag to attachments

Categories

(Developer Services :: Mercurial: bzexport, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jdm, Assigned: sfink)

References

Details

Attachments

(1 file, 3 obsolete files)

Sometimes you don't want a full review, but then you have to use the bugzilla interface and you become sad.
This applies on top of a pep8-compatibility patch. I should land that.
Assignee: nobody → sphink
Sorry, I've been sitting on this one for a while, mostly due to the lack of a test harness. But I've been using it long enough now, and Gijs just started implementing this separately, so I think it's time to land. Note that I did a fairly brutal rebase to get this one in landing position; I don't *think* I messed it up.

Maybe I should just land |hg pushed| and not tell anyone about it. It's truly awful, though. And yet I use it all the time... :( Rebasing past it is no fun.
Attachment #809423 - Flags: review?(josh)
Attachment #809403 - Attachment is obsolete: true
Doh! Lost the bz.py changes entirely in the rebase. (Fortunately still had them on the initial patch posted to this bug.)

Patch juggling is not going well for me today. Especially since I just discovered that my bzexport patch queue is not versioned. Need to add an mqext option to warn about that.
Attachment #809450 - Flags: review?(josh)
Attachment #809423 - Attachment is obsolete: true
Attachment #809423 - Flags: review?(josh)
Attachment #809450 - Flags: review?(josh) → review?(emorley)
Comment on attachment 809450 [details] [diff] [review]
Implement CC and feedback, also switch reviewers to comma-separated instead of fixed list of 2

I can't seem to get this to apply against the repo tip - do I need to apply a patch from one of the other bugs first?
Attachment #809450 - Flags: review?(emorley)
Hm, I must've rebased the patch at some point in the past, because I currently have it applied to the tip. Re-uploading.
Attachment #821126 - Flags: review?(emorley)
Attachment #809450 - Attachment is obsolete: true
Comment on attachment 821126 [details] [diff] [review]
Implement CC and feedback, also switch reviewers to comma-separated instead of fixed list of 2

Review of attachment 821126 [details] [diff] [review]:
-----------------------------------------------------------------

r=me with the 'flag_names[0]' corrected :-)

::: __init__.py
@@ +698,5 @@
>  
>      flag_ids = [ id for id in prodflags if flagdefs[str(id)]['name'] == flag_name ]
>  
>      if len(flag_ids) != 1:
> +        raise util.Abort(_("Could not find unique %s flag id") % flag_names[0])

Do you mean 'flag_name'?
Attachment #821126 - Flags: review?(emorley) → review+
(In reply to Ed Morley [:edmorley UTC+1] from comment #6)
> Comment on attachment 821126 [details] [diff] [review]
> Implement CC and feedback, also switch reviewers to comma-separated instead
> of fixed list of 2
> 
> Review of attachment 821126 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> r=me with the 'flag_names[0]' corrected :-)
> 
> ::: __init__.py
> @@ +698,5 @@
> >  
> >      flag_ids = [ id for id in prodflags if flagdefs[str(id)]['name'] == flag_name ]
> >  
> >      if len(flag_ids) != 1:
> > +        raise util.Abort(_("Could not find unique %s flag id") % flag_names[0])
> 
> Do you mean 'flag_name'?

The patch explicitly switches *away* from flag_name. Which makes no sense at all.

Can I blame it on rebasing? Or maybe plead insanity.

Anyway, thanks! Fixed.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Blocks: 936133
Blocks: 1022015
Product: Other Applications → Developer Services
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: