On 19/12/16 22:47, Adrian Bunk wrote:
> On Mon, Dec 19, 2016 at 10:15:33PM +0100, Daniel Pocock wrote:
>>
>>
>> On 19/12/16 21:57, Adrian Bunk wrote:
>>> On Thu, Dec 15, 2016 at 11:11:27AM +0100, Daniel Pocock wrote:
Is there any easy way to contact everybody who made a bug report
On Mon, Dec 19, 2016 at 10:15:33PM +0100, Daniel Pocock wrote:
>
>
> On 19/12/16 21:57, Adrian Bunk wrote:
> > On Thu, Dec 15, 2016 at 11:11:27AM +0100, Daniel Pocock wrote:
> >>
> >> Is there any easy way to contact everybody who made a bug report against
> >> a package and ask them to check if
On 19/12/16 21:57, Adrian Bunk wrote:
> On Thu, Dec 15, 2016 at 11:11:27AM +0100, Daniel Pocock wrote:
>>
>> Is there any easy way to contact everybody who made a bug report against
>> a package and ask them to check if the latest upload fixes it? Or is
>> there any script for maintainers to do
On Thu, Dec 15, 2016 at 11:11:27AM +0100, Daniel Pocock wrote:
>
> Is there any easy way to contact everybody who made a bug report against
> a package and ask them to check if the latest upload fixes it? Or is
> there any script for maintainers to do this?
I would expect the majority of your
On Sat, 17 Dec 2016, Wouter Verhelst wrote:
> On Thu, Dec 15, 2016 at 10:51:49AM -0600, Don Armstrong wrote:
> > That was me; sorry about that. Presumably you got all of the copies
> > because they were to different aliases which eventually ended up hitting
> > you.
>
> That reminds me of
On Thu, Dec 15, 2016 at 10:51:49AM -0600, Don Armstrong wrote:
> That was me; sorry about that. Presumably you got all of the copies
> because they were to different aliases which eventually ended up hitting
> you.
That reminds me of #784131. Is it possible to implement something along
those
On Thu, Dec 15, 2016 at 10:51:49AM -0600, Don Armstrong wrote:
> On Thu, 15 Dec 2016, Jonathan Dowland wrote:
> > In related news, I was surprised to receive 7 copies of a 1M
> > control@b.d.o email recently.
>
> That was me; sorry about that. Presumably you got all of the copies
> because they
On 15/12/16 17:43, Jonathan Dowland wrote:
> On Thu, Dec 15, 2016 at 11:26:52AM +0100, gregor herrmann wrote:
>> On Thu, 15 Dec 2016 11:11:27 +0100, Daniel Pocock wrote:
>>
>>> Is there any easy way to contact everybody who made a bug
>>> report against a package and ask them to check if the
On Thu, 15 Dec 2016, Jonathan Dowland wrote:
> In related news, I was surprised to receive 7 copies of a 1M
> control@b.d.o email recently.
That was me; sorry about that. Presumably you got all of the copies
because they were to different aliases which eventually ended up hitting
you.
[I had to
On Thu, Dec 15, 2016 at 11:26:52AM +0100, gregor herrmann wrote:
> On Thu, 15 Dec 2016 11:11:27 +0100, Daniel Pocock wrote:
>
> > Is there any easy way to contact everybody who made a bug report against
> > a package and ask them to check if the latest upload fixes it? Or is
> > there any script
On Thu, 15 Dec 2016, gregor herrmann wrote:
> On Thu, 15 Dec 2016 11:11:27 +0100, Daniel Pocock wrote:
> > Is there any easy way to contact everybody who made a bug report
> > against a package and ask them to check if the latest upload fixes
> > it? Or is there any script for maintainers to do
On Thu, 15 Dec 2016 11:11:27 +0100, Daniel Pocock wrote:
> Is there any easy way to contact everybody who made a bug report against
> a package and ask them to check if the latest upload fixes it? Or is
> there any script for maintainers to do this?
I'm not sure this is a good idea ... Anyway,
Is there any easy way to contact everybody who made a bug report against
a package and ask them to check if the latest upload fixes it? Or is
there any script for maintainers to do this?
If somebody has opened 2 ore more bugs maybe they may prefer to only
receive a single email summarizing all
13 matches
Mail list logo
