On 26 Nov 2009, at 01:10, David Chisnall wrote:
> On 26 Nov 2009, at 00:50, Nicola Pero wrote:
>
>>> I'd be in favour of ditching NEWS and ChangeLog.
>>>
>>> ChangeLog has less information, in a less useful format, than the svn logs
>>> and is a hold-over from CVS not storing repository-wide c
ChangeLog has less information, in a less useful format, than the
svn logs and is a hold-over from CVS not storing repository-wide
change information sensibly. With svn log, you can get a log of
change messages at any granularity that you like.
I agree there is an overlap, but there are
It would be good to consider exactly how much (if any) information
we want to present in NEWS/ReleaseNotes ... my preference would be
for minimal information there, and a pointer to a generated
ChangeLog for details.
This would require a policy that svn log entries should be suitable
f
So I guess the solution to that would be instead to require
ChangeLog entries to be committed to svn log.
By the way, presumably we'd still include the author of the change in
the subversion commit message ?
Ie, we write a full ChangeLog entry including the author at the
beginning ?
The r
On 26 Nov 2009, at 11:03, Nicola Pero wrote:
>
>> It would be good to consider exactly how much (if any) information we want
>> to present in NEWS/ReleaseNotes ... my preference would be for minimal
>> information there, and a pointer to a generated ChangeLog for details.
>> This would requir
On 26 Nov 2009, at 11:08, Nicola Pero wrote:
>> So I guess the solution to that would be instead to require ChangeLog
>> entries to be committed to svn log.
>
> By the way, presumably we'd still include the author of the change in the
> subversion commit message ?
> Ie, we write a full ChangeL
On 26 Nov 2009, at 11:08, Nicola Pero wrote:
By the way, presumably we'd still include the author of the change
in the subversion commit message ?
Ie, we write a full ChangeLog entry including the author at the
beginning ?
Yes. If you look in the LLVM svn log, for example, you will see a f
It's not a strict requirement.
On Wednesday, November 25, 2009, wrote:
>
>
>
> I still haven't seen a convincing argument for it. Any of the information
> that people write in the ChangeLog file they could also write in the commit
> log. It is impossible to make a commit without writing a log
On Thu, Nov 26, 2009, Nicola Pero wrote:
> I also occasionally work on gnustep-make offline, and the subversion
> logs are not available offline, while ChangeLogs are.
Dare I say it, but the obvious answer to that is a DVCS,
of which hg and git spring to mind.
On Thu, Nov 26, 2009 at 11:08:01AM
David Chisnall wrote:
On 25 Nov 2009, at 22:39, Richard Frith-Macdonald wrote:
There are actually three levels of change information ...
NEWS ... just the headlines
ReleaseNotes ... some more detail
ChangeLog ... everything
Maybe you are right and we shouldn't bother with NEWS? I'd be
inter
Hi,
I agree with Nicola here ... it's very, very far from being a waste of space
... people do need to be able to see the changes made to the code.
So your suggestion of having a script make a ChangeLog automatically from the
svn logs makes a *lot* of sense.
WasteOfSpace? I think that is
On Thu, Nov 26, 2009 at 10:15 PM, Riccardo Mottola wrote:
> David Chisnall wrote:
>>
>> On 25 Nov 2009, at 22:39, Richard Frith-Macdonald wrote:
>>
>>> There are actually three levels of change information ...
>>> NEWS ... just the headlines
>>> ReleaseNotes ... some more detail
>>> ChangeLog ...
Hi,
By the way, presumably we'd still include the author of the change in
the subversion commit message ?
Ie, we write a full ChangeLog entry including the author at the
beginning ?
The reason is that when we receive patches, the committer is often
*not* the author of the patch, only the revi
On 26 Nov 2009, at 22:15, Riccardo Mottola wrote:
Not only in a ChangeLog I can write more than in a commit and I can
group files and comment on sigle pieces of them, but it is an easy
file I can check.
Are you using a different svn to me? When I do a commit, it pops up
$EDITOR (vim in
14 matches
Mail list logo