On Vi, 10 sep 21, 20:22:43, Steve Dondley wrote:
>
> Yeah, had I known my bug report would be thrown in the subject, I would have
> changed things up a bit.
The report should still go in the message body, the subject (and bug
title) is supposed to represent a concise summary.
For reference, the
Hi,
11 sept. 2021, 18:52 de a...@cityscape.co.uk:
> It's your submission; you can close it, In fact, any user can clos
> it.
>
By the way, how can one see that a bug is closed and not open please?
For example, I know that the bug #958402 [1] has been closed because I received
an email notifica
It doesn't state how the originator of the bug report can close it.
Send a mail to xx-d...@bugs.debian.org. Give a reason for the
closure.
Got it. Thanks for the help.
On Sat 11 Sep 2021 at 12:44:30 -0400, Steve Dondley wrote:
> On 2021-09-11 06:27 AM, Brian wrote:
> > On Fri 10 Sep 2021 at 20:22:43 -0400, Steve Dondley wrote:
> >
> > > On 2021-09-10 08:15 PM, Greg Wooledge wrote:
> > > > On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
> > > > >
On 2021-09-11 06:27 AM, Brian wrote:
On Fri 10 Sep 2021 at 20:22:43 -0400, Steve Dondley wrote:
On 2021-09-10 08:15 PM, Greg Wooledge wrote:
> On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
> >
> > > Can I just leave this as is? Or can/should I correct it somehow?
> >
> > Ok, wh
On Fri 10 Sep 2021 at 20:22:43 -0400, Steve Dondley wrote:
> On 2021-09-10 08:15 PM, Greg Wooledge wrote:
> > On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
> > >
> > > > Can I just leave this as is? Or can/should I correct it somehow?
> > >
> > > Ok, while I was writing that las
On 11/09/2021 01:25, Steve Dondley wrote:
This may happen in a timely manner, or it may not. Your best bet at
this point is to wait a few days and see what happens. If nobody
fixes it up before then, you might consider replying to the bug and
supplying an actual description of the bug.
OK,
This may happen in a timely manner, or it may not. Your best bet at
this point is to wait a few days and see what happens. If nobody
fixes it up before then, you might consider replying to the bug and
supplying an actual description of the bug.
OK, sounds like a plan. I see in the link I pr
On 2021-09-10 08:15 PM, Greg Wooledge wrote:
On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
> Can I just leave this as is? Or can/should I correct it somehow?
Ok, while I was writing that last email, I got another confirmation:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug
On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
>
> > Can I just leave this as is? Or can/should I correct it somehow?
>
> Ok, while I was writing that last email, I got another confirmation:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994068
>
> So I'm probably good?
Can I just leave this as is? Or can/should I correct it somehow?
Ok, while I was writing that last email, I got another confirmation:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994068
So I'm probably good?
I used reportbug for the first time. The experience was a little
confusing.
It appears to have gone through because I got an confirmation email:
Email subject:
1.4.11+dfsg.1-4: Please see issue at github:
https://github.com/roundcube/roundcubemail/issues/8198
Email body:
12 matches
Mail list logo