Re: [geclipse-dev] Submitting patches

[Ariel Garcia <garcia@xxxxxxxxxx>]

Hi,

> Yes, that's one reason *not* to maintain this redundant information in
> the database.

i am lost... yes to what?  ;-)

It is OK for me to add some "tag" or pseudo-tag like [patch] in the title 
if the bug is _opened by a contributor_  as the way to get his code 
integrated into the SVN repo. 
Normal ("real") bugs which later get patches submitted shouldn't get their 
title changed (if at all possible in BZ)  or a second bug be opened just 
to contain the patch!

SO: 
   +1 for [patch] if contributor just wants to get a patch included
   -1  for extra/duplicate bugs just for patches
   -1 for changing the bug title

:-)

> As an example use this URL to create a list of open g-Eclipse bugs with
> attached patches:
>
> https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_de
...

well that one finds just 3 bugs, so these are definitely not all bugs with 
patches ;-)

> But I also have bug-items, which are really bugs. And after fixing this
> bug I have to create patch. Should I add "[patch]" to the title also in
> this case?

all _real_ bugs are supposed to end up in a bugfix at some point. And it 
doesn't make sense to start with [patch] all the bug reports.

So, no, Markus solution of using the search functionality in Bugzilla is 
the only reasonable one in my opinion. Why duplicate info.

> I suggest creating a new bug-item for the patch in which you refer to
> the original bug report. And on the other hand you also should then
> refer from the bug report to the patch item when marking it as fixed.
> Objections?

oh, yes, me! ;-)  having to create a second bug and crossref them both 
toghether makes for a lot of overhead and it is very error prone 
(forgetting to add the ref number in one makes life complicated already)

Ariel