Don Armstrong wrote:
When working with NMUs, you can either
1) Incorporate the NMU changelog entries before your new changelog entry
2) Include a separate section in your new changelog entry which
acknowledges the NMU-specific changes and the bugs that they fixed
without including the NMU
On Tue, 05 Aug 2014, Yavor Doganov wrote:
Don Armstrong wrote:
When working with NMUs, you can either
1) Incorporate the NMU changelog entries before your new changelog entry
2) Include a separate section in your new changelog entry which
acknowledges the NMU-specific changes and
Paul Gevers wrote:
I have several (in random order) remarks:
Please acknowledge nmus (even if the content is nearly all yours)
Fixed in Git. BTW, this Ack NMU thing doesn't seem to work as
before. Previously, the maintainer would also close the bug that was
fixed by the NMU, and IIRC this
On Mon, 04 Aug 2014, Yavor Doganov wrote:
Paul Gevers wrote:
Please acknowledge nmus (even if the content is nearly all yours)
Fixed in Git. BTW, this Ack NMU thing doesn't seem to work as
before. Previously, the maintainer would also close the bug that was
fixed by the NMU, and IIRC this
Control: owner -1 !
Control: tags -1 moreinfo
Hi Yavor,
On Sun, 15 Jun 2014 10:45:38 +0300 Yavor Doganov ya...@gnu.org wrote:
I am looking for a sponsor for my package gridlock.app.
I have several (in random order) remarks:
Please acknowledge nmus (even if the content is nearly all yours)
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package gridlock.app.
It builds these binary packages:
gridlock.app - Collection of grid-based board games for GNUstep
To access further information about this package, please visit the
following
6 matches
Mail list logo
