Phil Holmes writes Saturday, September 28, 2013 2:19 PM
> From: "David Kastrup"
>> "Phil Holmes" writes:
>>
>>> There is a question in my mind as to what a) should bump the version
>>> to: i) current version; or ii) version that the update related to.
>>> Simplest is probably i).
>>
>> Uh, i)
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Saturday, September 28, 2013 1:36 PM
Subject: Re: LSR imports and version numbers?
"Phil Holmes" writes:
The bumping of version numbers is a pain for me, too - it makes it
ted
"Phil Holmes" writes:
> The bumping of version numbers is a pain for me, too - it makes it
> tedious to check what makelsr has _really_ done.
>
> I think we should have 2 alternatives: a) bump the version if the file
> is updated, and not if it hasn't or b) bump to the current version
> regardles
- Original Message -
From: "David Kastrup"
To:
Sent: Saturday, September 28, 2013 1:25 PM
Subject: LSR imports and version numbers?
Hi,
I've seen the last LSR import do nothing but bump the version number on
a large number of files from 2.17.25 to 2.15.27. Now th
Hi,
I've seen the last LSR import do nothing but bump the version number on
a large number of files from 2.17.25 to 2.15.27. Now that's consistent
with the current documentation on convert-ly which states:
The following options can be given:
-d,--diff-version-update
increase the \version
