[Bf-committers] Re: [Bf-blender-cvs] CVS
commit: blender/source/blender/src editmesh_add.c
rob at captainvideo.nl
Thu Jan 13 16:11:05 CET 2005
I admit that i broke the rules regarding committing in someone else's
code, and i apologise for that.
But as you state yourself, it's a very minor issue and concerns a very
minor commit. It was never my
intention to disregard the amount of recoding, i was merely afraid that
Blender would loose it's
uniqueness due to this missing notice. Just putting the smile back on
the face of the Blender user.
Having said that, i really regret that the attention of this minor
commit is growing way out of proportions.
If the small notice doesn't fit in any rewriting plans or schedules,
erase it. I won't touch it again.
Ton Roosendaal wrote:
> Hi Rob,
> If you have issues with changes in code by other people you should
> notify the maintainer first instead of re-committing back changes.
> That applies anyone with CVS write access, and is a basic rule to
> ensure smooth and pleasant cooperation.
> The monkey primitive was promoted to be a normal primitive last
> september, as mentioned in the CVS log. Was part of the enormous
> amount of work done on mesh editing.
> Its a very minor issue, I know that. But still doesn't make it a good
> On 12 Jan, 2005, at 14:14, Alexander Ewering wrote:
>> On Wed, 12 Jan 2005, Rob Haarsma wrote:
>>> phase (Rob Haarsma) 2005/01/12 13:25:56 CET
>>> Modified files:
>>> blender/source/blender/src editmesh_add.c
>>> Let's keep Blender a monkey app.
>> Thanks, one of the most sensible commits in the past days ;-)
>> Blender was already growing much too professional... (seriously!)k
>> | alexander ewering instinctive mediaworks
>> | ae[@]instinctive[.]de http://www[.]instinctive[.]de
>> Bf-committers mailing list
>> Bf-committers at projects.blender.org
> Ton Roosendaal Blender Foundation ton at blender.org
> Bf-committers mailing list
> Bf-committers at projects.blender.org
More information about the Bf-committers