Ross Vandegrift writes:
> On Tue, Oct 17, 2017 at 09:23:57AM +1100, Ben Finney wrote:
> > As someone who went looking for it recently when you didn't know the
> > recommendation: Where exactly would you expect to find this
> > information, which particular section of Policy
Hi Ben - thanks fo the thorough explanation, much appreciated!
On Tue, Oct 17, 2017 at 09:23:57AM +1100, Ben Finney wrote:
> So now that we agree it's not too clear, and may be difficult to find, I
> would welcome a bug report against Policy for clarifying this issue.
>
> As someone who went
Ross Vandegrift writes:
> On Mon, Oct 16, 2017 at 11:54:20AM +1100, Ben Finney wrote:
> > Ross Vandegrift writes:
> > > Good question. I guess I think of a changelog as history - so changes
> > > I made on 1.15 go with 1.15 whether it was released or not.
> >
On Mon, Oct 16, 2017 at 11:54:20AM +1100, Ben Finney wrote:
> Ross Vandegrift writes:
> > Good question. I guess I think of a changelog as history - so changes
> > I made on 1.15 go with 1.15 whether it was released or not.
>
> Thanks for explaining your perspective.
>
> That
On Mon, Oct 16, 2017 at 11:54:20AM +1100, Ben Finney wrote:
> Ross Vandegrift writes:
> > On Sun, Oct 15, 2017 at 12:14:59AM +0200, Mattia Rizzolo wrote:
> > > Rather, I have a counter-question for you: why are you keeping
> > > entries for unreleased uploads in d/changelog? I
Ross Vandegrift writes:
> On Sun, Oct 15, 2017 at 12:14:59AM +0200, Mattia Rizzolo wrote:
> > Rather, I have a counter-question for you: why are you keeping
> > entries for unreleased uploads in d/changelog? I find it rather
> > confusing, mostly useless and with no real
On 10/15/2017 05:36 AM, Ross Vandegrift wrote:
> Good question. I guess I think of a changelog as history - so changes I
> made on 1.15 go with 1.15 whether it was released or not. But if I
> think of the changelog as telling others about changes in a release,
> then it makes sense to squash
On Sun, Oct 15, 2017 at 12:14:59AM +0200, Mattia Rizzolo wrote:
> > Thanks for the hint. dpkg-genchanges(1) says -c requires a version. Is
> ^
> I'll assume this is a typo and you meant -v
whoops yes!
> > there a
On Sat, Oct 14, 2017 at 02:14:30PM -0700, Ross Vandegrift wrote:
> On Sat, Oct 14, 2017 at 11:53:25PM +0500, Andrey Rahmatullin wrote:
> > It's not BTS, it's dpkg-genchanges. Pass a proper -v to the command you
> > use to build the package.
>
> Thanks for the hint. dpkg-genchanges(1) says -c
On Sat, Oct 14, 2017 at 11:53:25PM +0500, Andrey Rahmatullin wrote:
> It's not BTS, it's dpkg-genchanges. Pass a proper -v to the command you
> use to build the package.
Thanks for the hint. dpkg-genchanges(1) says -c requires a version. Is
there a downside to always starting from the first
On Sat, Oct 14, 2017 at 11:53:25PM +0500, Andrey Rahmatullin wrote:
> On Sat, Oct 14, 2017 at 11:33:24AM -0700, Ross Vandegrift wrote:
> > Hi all,
> >
> > My changelog [1] documents versions that weren't released. I like
> > including that info (it's been useful for me). But the BTS doesn't
On Sat, Oct 14, 2017 at 11:33:24AM -0700, Ross Vandegrift wrote:
> Hi all,
>
> My changelog [1] documents versions that weren't released. I like
> including that info (it's been useful for me). But the BTS doesn't pick
> up on Closes from those - even though later versions have been uploaded.
Hi all,
My changelog [1] documents versions that weren't released. I like
including that info (it's been useful for me). But the BTS doesn't pick
up on Closes from those - even though later versions have been uploaded.
Is there a way to make the BTS notice these entries - or do I need to
13 matches
Mail list logo