Okay, this change has been made. Please refrain from using the PATCH issue
tracker type from now on. If you have a patch to post to a new tracker
item, create the item as a DEFECT or ENHANCEMENT or FEATURE, attach the
patch, and add the 'patch' keyword to the issue.
Thanks all!
-- With love, an
Hi C. Michael,
As a developer of non-svn stuff and a user of svn, not a developer of
svn, I support your notion that PATCH doesn't have any meaning.
I might also make the same comment about TASK. But that's another
issue for another day.
Craig
On May 7, 2010, at 9:39 AM, C. Michael Pilat
On Fri, May 07, 2010 at 12:39:05PM -0400, C. Michael Pilato wrote:
> I've never been a fan of the PATCH issue type present in our tracker. While
> the other issue types (TASK, DEFECT, ENHANCEMENT, FEATURE) tell you
> something about the problem that needs a-fixin', PATCH tells you only that
> some
I've never been a fan of the PATCH issue type present in our tracker. While
the other issue types (TASK, DEFECT, ENHANCEMENT, FEATURE) tell you
something about the problem that needs a-fixin', PATCH tells you only that
someone has proposed some code change. But for what?
So in the ViewVC project
4 matches
Mail list logo
