Stefan Sperling wrote:
> It won't be a single file :)
Darn. I thought it was with notify.c.
>
> Basically, conflict stat gathering needs to be moved into
> the client library, and be done per-operation. Users of the
> client library should be able to receive conflict stats as
> part of the result of an API call such as svn_client_update().
>
> Right now, the conflict stats are gathered purely inside
> the command line client, based on notifications received
> from the client library. This is a bit of a hack, and cannot
> easily be made as accurate as we'd like it to be, hence issue #3342.
> Pushing this down into the client library would also benefit
> other clients such as TortoiseSVN.
Well, I think I'll re-clarify my position with this issue.
I'm still reading (as stated in the hacking.html) the .h
files trying to understand the layout and whilst doing that,
learning C.
>
> If you feel this is too overwhelming, don't rush into it.
I'll definitely be taking my time here.
> Just keep fixing simple problems like you did for issue #3207.
> Doing this really helps the project, and you will gain more
> confidence and learn more about the code as you go along.
I would agree. Right now, I'm definitely on the shaky side
but it's good to learn a new language.
> The amount of problems that need to be fixed is really large anyway.
> There should be many little problems that need little fixes.
I've dumped the issues(NEW, FEATURE, ENHANCE, and TASK) and their
descriptions to a local html setup so I can read up on the
information locally. That's how I picked up #3207.
> Most importantly, just do what is fun!
Thanks Stefan! Very much appreciate the help.
Edmund
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1542736
Received on 2009-04-04 16:31:48 CEST