On Tue, Oct 09, 2018 at 04:06:21PM +0200, Elrond wrote:
> On Mon, Oct 08, 2018 at 21:33:09 -0400, James McCoy wrote:
> [...]
> > Please don't completely repurpose old bugs. If there's something new to
> > fix, the open a new bug.
> >
> > Cheers,
>
> Understood!
>
> Should I close/undo/archive t
On Mon, Oct 08, 2018 at 21:33:09 -0400, James McCoy wrote:
[...]
> Please don't completely repurpose old bugs. If there's something new to
> fix, the open a new bug.
>
> Cheers,
Understood!
Should I close/undo/archive this one and file a fresh one?
Or should we leave it like it is?
Cheers
On Sun, Oct 07, 2018 at 12:13:45PM +0200, Elrond wrote:
> the exact same that applied to vim-runtime now applies
> also to vim-common.
>
> Please add Multi-Arch: foreign to vim-common too.
Please don't completely repurpose old bugs. If there's something new to
fix, the open a new bug.
Cheers,
-
Hi,
the exact same that applied to vim-runtime now applies
also to vim-common.
Please add Multi-Arch: foreign to vim-common too.
Thanks
Elrond
4 matches
Mail list logo