On 2011-02-13, Andreas Tille wrote:
> On Sat, Feb 12, 2011 at 09:47:22PM +0100, Julien Cristau wrote:
>> On Sun, Feb 6, 2011 at 16:51:26 +0100, Andreas Tille wrote:
>> > 3. Whether changelogs should be branched for different Debian
>> > releases, be it testing-proposed-updates, backports o
On Sat, Feb 12, 2011 at 09:47:22PM +0100, Julien Cristau wrote:
> On Sun, Feb 6, 2011 at 16:51:26 +0100, Andreas Tille wrote:
>
> > 3. Whether changelogs should be branched for different Debian
> > releases, be it testing-proposed-updates, backports or even
> > derivatives as Ubuntu o
On Sun, Feb 6, 2011 at 16:51:26 +0100, Andreas Tille wrote:
> 3. Whether changelogs should be branched for different Debian
> releases, be it testing-proposed-updates, backports or even
> derivatives as Ubuntu or others.
>
As the package itself is branched, the changelog should be, t
Andreas Tille writes:
> [Reply-To set to debian-devel]
>
> Hi,
>
> on the Debian Med list a discussion about handling changelogs was started[1]
> which addressed the following questions:
>
> 1. What to do with pre-Debian-Release changelogs (if packaging
> needed some time and went through
On Sun, Feb 06 2011, Andreas Tille wrote:
>
> 2. Whether upstream changelogs should be copied fully or in
> parts copied into Debian changelog and I think the New
> maintainers guide[3] gives a clear answer to mention only
> the changes of this *new* release specifically if these
5 matches
Mail list logo
