[Bf-committers] Re: [Bf-blender-cvs] CVS commit: blender/source/blender/src space.c
Thu, 11 Dec 2003 15:14:12 +0100
I sugest the following for a cvs report on bug fix:
- summarize the bugreport (usually end user level)
- mention what the real problem was (coder level, can be different from
- mention what you did to solve it
You are free to add links to the tracker, bug numbers, websites, etc.
But I prefer to be able to read a cvs report stand-alone as well. For
example when a report moves to another tracker, a URL becomes invalid.
Most important is (OK, for me!) to be able to make quick & efficiently
the release notes. Last time I had to do too much research for some
reports to find out what actually was done. Especially when it is on
parts of code I don't maintain.
I think this way, cvs mails become a good resource, and interesting
read for everyone as well.
On Thursday, Dec 11, 2003, at 05:12 Europe/Amsterdam, Martin Poirier
> If I post links to the bugtracker, that's ok?
> In a nutshell, Goof forgot to add a displist refresh
> call in space.c when calling merge, so the subsurf
> wouldn't update.
> --- Chris Want <firstname.lastname@example.org> wrote:
>> About commit messages again ... I personally would
>> really like to see a bit of a description of the
>> bug that was fixed, not just a number -- especially
>> now that #794 is closed and is no longer in the
>> tracker list I have no idea whether this refered to
>> meta-balls, or armatures, or what?
>> Martin Poirier wrote:
>>> theeth (Martin Poirier) 2003/12/11 05:00:52 CET
>>> Modified files:
>>> blender/source/blender/src space.c
>>> Fixed bug #794
>>> The displist needed to be updated
>>> Revision Changes Path
>>> 1.107 +3 -1
>>> Bf-blender-cvs mailing list
>> Bf-committers mailing list
> Do you Yahoo!?
> New Yahoo! Photos - easier uploading and sharing.
> Bf-committers mailing list
Ton Roosendaal Blender Foundation email@example.com