Assigning a bug to myself

[Alexandros Dermenakis]

Hi,

I 'm now ready to start debugging wine so I'd like to try solving a bug. Do I 
need to assign a bug to myself or I just start solving it? If I have to assign 
it how can I do that?

I created a bug zilla account

[Ben Klein]

2009/8/10 Alexandros Dermenakis :
> Hi,
>
> I 'm now ready to start debugging wine so I'd like to try solving a bug. Do I
> need to assign a bug to myself or I just start solving it? If I have to assign
> it how can I do that?
>
> I created a bug zilla account

You don't need to assign bugs to yourself. I believe this was covered
in another thread. Once you have a patch to fix a bug, send it to
wine-patches, following the "submitting patches" guide. Then, if it is
accepted and committed, the appropriate bug can be marked "FIXED".

Debugging tools

[Alexandros Dermenakis]

Hi,

I would like some help about which tools to use for editing code, searching 
through the source files etc. also, is there a way to import all the source 
code in Kdevelop?

thanks

Debugging tools

[Austin English]

On Sun, Aug 9, 2009 at 10:50 PM, Alexandros
Dermenakis wrote:
> Hi,
>
> I would like some help about which tools to use for editing code, searching
> through the source files etc. also, is there a way to import all the source
> code in Kdevelop?

To get the source:
http://wiki.winehq.org/GitWine

for a ton more stuff:
http://wiki.winehq.org/Developers

Debugging tools

[André Hentschel]

Alexandros Dermenakis schrieb:
> Hi,
>
> I would like some help about which tools to use for editing code, searching 
> through the source files etc. also, is there a way to import all the source 
> code in Kdevelop?
>
> thanks

I mostly edit the files with Geany(geany.org), but thats a matter of taste.
Also i use source.winehq.org to find functions and defines.
I just would try to use Kdevelop, but i dont know if it will work.

Debugging tools

[Alex Dermenakis]

> I just would try to use Kdevelop, but i dont know if it will work.

Actually KDevelop works. I created a new empty project and Imported the
whole git repository and
I chose to use wine's custom MakeFile and configure files. I'm not able
though to start the debug properly
but I'm working on it.

thanks for the help guys ;-)

[Hin-Tak Leung]

--- On Mon, 10/8/09, Ben Klein  wrote:
> 2009/8/10 Alexandros Dermenakis
> :
> > Hi,
> >
> > I 'm now ready to start debugging wine so I'd like to
>
> try solving a bug. Do I
> > need to assign a bug to myself or I just start solving
>
> it? If I have to assign
> > it how can I do that?
> >
> > I created a bug zilla account
>
> You don't need to assign bugs to yourself. I believe this
> was covered
> in another thread. Once you have a patch to fix a bug, send
> it to
> wine-patches, following the "submitting patches" guide.
> Then, if it is
> accepted and committed, the appropriate bug can be marked
> "FIXED".

To avoid duplication of effort (though quite unlikely among the wine community), it is probably appropriate to stick a comment on the specific bug to that effect and put yourself to the CC:. This way, others know you are working on it, and you get to read about others' insight to the problem if they choose to write to comment. (this has essentially the same effect as having the bug formally assigned to oneself, without the management/administration overhead).

Most bugs' status are eventually and officially closed by AJ anyway :-).