On Mon, 2011-10-10 at 08:51 +0100, JasonW wrote:
On 10 October 2011 01:25, Nigel Taylor njtay...@asterisk.demon.co.uk wrote:
On 10/09/11 17:13, bat guano wrote:
I think that would be a good feature.
Some programs (such as FFmpeg-git) show the 'commit'.
Releases should be made
On 09/10/2011 17:13, bat guano wrote:
Some programs (such as FFmpeg-git) show the 'commit'.
The version string with commit ID is inserted into FFmpeg when it is
compiled. The process relies on having access to a clone of the git
repo in order to retrieve the commit history. Look at
On 10/10/2011 01:25, Nigel Taylor wrote:
There are only two changes to the get_iplayer script, since v2.80 was
tagged in git. The other 4 changes are specific to windows, related to
the windows installer. The need for a v2.81 yet may be open to debate.
As to whether a v2.81 release is
With all the incremental changes made by dinkypumpkin (and others) to
the 2.80 perl script, I was thinking it might be a good thing to
somehow distinguish between them quickly...
Perhaps instead of x.yy maybe x.yy-yymmdd ? Just something to make it
obvious without having to do a diff/similar.
With all the incremental changes made by dinkypumpkin (and others) to
the 2.80 perl script, I was thinking it might be a good thing to
somehow distinguish between them quickly...
Hi
I think that would be a good feature.
Some programs (such as FFmpeg-git) show the 'commit'.
On 10/09/11 17:13, bat guano wrote:
With all the incremental changes made by dinkypumpkin (and others) to
the 2.80 perl script, I was thinking it might be a good thing to
somehow distinguish between them quickly...
Hi
I think that would be a good feature.
Some programs (such as
6 matches
Mail list logo
