Your message dated Sat, 5 Nov 2011 00:36:21 +0100
with message-id
<CAPdtAj16KXpPrgGRJXuAfp_RKFyKWu6+qqr-wDG=-t1qj+x...@mail.gmail.com>
and subject line Re: Bug#614162: reportbug: Allow to report more than one bug
has caused the Debian Bug report #614162,
regarding reportbug: Allow to report more than one bug
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
614162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614162
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 4.12.6
Severity: wishlist
Ahoy,
I usually report more that one bug at a time. I may have a short list of
bugs, or I may have found something interesting in the bugs list, added
more info to that report, and now would like to proceed to report the bug I
had in mind before that. For these situations, it would be nice if the last
screen (the one with the confusing Cancel-Apply buttons and the badly
wrapped text) had a button allowing one to start a new report.
To generalize that request, it could be a good idea to add a button (say on
the bottom left of the GTK UI, so that it’s not mixed with the
Cancel/Continue
buttons that apply to the current report) that can launch a new window (or
tab, but that’s another request I opened) at any time.
The net benefit is that people could launch the program and do more than
one report or reply without having to launch it again.
One obvious drawback of this idea is that one crash would make you lose
more that one report. Possible workarounds: launch a new process instead
of a new window in the same process; auto-save reports in progress in $TMP;
fix the damn GTK float bug <wink>.
sneaking-bug-reports-in-parens-ly yours
-- Package-specific info:
** Environment settings:
EDITOR="vim"
DEBEMAIL="[email protected]"
DEBFULLNAME="Éric Araujo"
INTERFACE="gtk2"
** /home/wok/.reportbugrc:
reportbug_version "3.48"
mode standard
ui gtk2
realname "Éric Araujo"
email "[email protected]"
smtphost "smtp.orange.fr"
bts debian
check-available
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages reportbug depends on:
ii apt 0.8.10.3 Advanced front-end for dpkg
ii python 2.6.6-3+squeeze5 interactive high-level object-orie
ii python-reportbug 4.12.6 Python modules for interacting wit
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn debconf-utils <none> (no description available)
ii debsums 2.0.48+nmu3 tool for verification of installed
ii dlocate 1.02 fast alternative to dpkg -L and dp
ii dma [mail-transport-age 0.0.2010.06.17-6 lightweight mail transport agent
ii emacs23-bin-common 23.2+1-7 The GNU Emacs editor's shared, arc
ii file 5.04-5 Determines file type using "magic"
ii gnupg 1.4.10-4 GNU privacy guard - a free PGP rep
ii python-gtk2 2.17.0-4 Python bindings for the GTK+ widge
ii python-gtkspell 2.25.3-7 Python bindings for the GtkSpell l
ii python-urwid 0.9.9.1-1 curses-based UI/widget library for
ii python-vte 1:0.24.3-2 Python bindings for the VTE widget
ii xdg-utils 1.1.0~rc1-1 desktop integration utilities from
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
On Fri, Feb 25, 2011 at 00:25, Sandro Tosi <[email protected]> wrote:
> user [email protected]
> usertags 614162 ui-gtk
> thanks
>
> Hi Éric,
>
> On Sun, Feb 20, 2011 at 01:44, Éric Araujo <[email protected]> wrote:
>> I usually report more that one bug at a time. I may have a short list of
>> bugs, or I may have found something interesting in the bugs list, added
>> more info to that report, and now would like to proceed to report the bug I
>> had in mind before that. For these situations, it would be nice if the last
>> screen (the one with the confusing Cancel-Apply buttons and the badly
>> wrapped text) had a button allowing one to start a new report.
>>
>> To generalize that request, it could be a good idea to add a button (say on
>> the bottom left of the GTK UI, so that it’s not mixed with the
>> Cancel/Continue
>> buttons that apply to the current report) that can launch a new window (or
>> tab, but that’s another request I opened) at any time.
>>
>> The net benefit is that people could launch the program and do more than
>> one report or reply without having to launch it again.
>
> Please consider it's a *huge* change in reportbug way of working, so
> don't expect anything soon.
On a second thought, I'm sorry but this won't be implemented.
Reportbug aims at report one bug at a time, and the few cases where
more than one should be filed could be covered by simply re-executing
reportbug.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
