You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Branko Čibej <br...@xbc.nu> on 2004/05/16 21:57:01 UTC

Anyone looking for a nice and easy bite-sized task?

Have you always wanted to contribute to the Subversion code, but were 
unsure where to start? This is your chance!

    http://subversion.tigris.org/issues/show_bug.cgi?id=1861

This issue will take you on a guided tour of _all_ the Subversion 
libraries, but you will not have to confront the darker magic dwelling 
in them. After your tour is complete, you will send a patch to the dev@ 
list; if it is accepted (there has to be /some/ kind of exit exam), you 
will be counted among the contributers to Subversion 1.1.

Are you up to the challenge! Click the link today!

-- Brane

/me doesn't mention that fact that it's brain-dead, but necessary work 
he wants to fob off on some willing victim :-)



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Anyone looking for a nice and easy bite-sized task?

Posted by Branko Čibej <br...@xbc.nu>.
Edmund Horner wrote:

> Branko Čibej wrote:
>
>> Have you always wanted to contribute to the Subversion code, but were 
>> unsure where to start? This is your chance!
>>
>>    http://subversion.tigris.org/issues/show_bug.cgi?id=1861
>>
>> This issue will take you on a guided tour of _all_ the Subversion 
>> libraries, but you will not have to confront the darker magic 
>> dwelling in them. After your tour is complete, you will send a patch 
>> to the dev@ list; if it is accepted (there has to be /some/ kind of 
>> exit exam), you will be counted among the contributers to Subversion 
>> 1.1.
>>
>> Are you up to the challenge! Click the link today!
>>
>> -- Brane
>>
>> /me doesn't mention that fact that it's brain-dead, but necessary 
>> work he wants to fob off on some willing victim :-)
>
>
> I'm happy to do it, but it might be a 48-hour job... meaning I've got 
> an exam tomorrow.

Oh, as long as it's in time for 1.1, that's no problem.

> <quote>
> Now that the version query/check infrastructure is in the code, we 
> should add
>
> a) Version query functions to all svn libraries;
>    see include/svn_client.h, libsvn_client/version.c
>
> b) Version checks to all command-line clients;
>    see clients/cmdline/main.c:check_lib_versions
> </quote>
>
> I take it it's just a) duplicating the version changes to 
> libsvn_client to the other libraries (with appropriate naming); and b) 
> duplicating clients/cmdline/main.c:check_lib_versions() to svnadmin, 
> svnlook, svninfo, svndumpfilter, svnversion (with appropriate lists of 
> libraries)?

That's correct.

Thanks for taking this up! Don't forget to assign the issue to yourself 
and mark it as "started".

-- Brane




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Anyone looking for a nice and easy bite-sized task?

Posted by Branko Čibej <br...@xbc.nu>.
Edmund Horner wrote:

> Edmund Horner wrote:
>
>> I'm happy to do it, but it might be a 48-hour job... meaning I've got 
>> an exam tomorrow.
>
>
> Well I've started... but I realise I don't have a clear idea of what 
> the right list of libraries to check for each executable is.  For 
> example, the pre-existing clients/cmdline/main.c has:
>
>       { "svn_subr", svn_subr_version },
>       { "svn_client", svn_client_version },
>
> Does this mean it's sufficient to test only the libraries the 
> executable links directly with (and not worry about things used by 
> svn_client, etc.) ?

Yes. The 'libraries' lists in build.conf are (should be) definitive.




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Anyone looking for a nice and easy bite-sized task?

Posted by Edmund Horner <ch...@chrysophylax.cjb.net>.
Edmund Horner wrote:
> I'm happy to do it, but it might be a 48-hour job... meaning I've got an 
> exam tomorrow.

Well I've started... but I realise I don't have a clear idea of what the 
right list of libraries to check for each executable is.  For example, 
the pre-existing clients/cmdline/main.c has:

       { "svn_subr", svn_subr_version },
       { "svn_client", svn_client_version },

Does this mean it's sufficient to test only the libraries the executable 
links directly with (and not worry about things used by svn_client, etc.) ?


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Anyone looking for a nice and easy bite-sized task?

Posted by Edmund Horner <ch...@chrysophylax.cjb.net>.
Branko Čibej wrote:
> Have you always wanted to contribute to the Subversion code, but were 
> unsure where to start? This is your chance!
> 
>    http://subversion.tigris.org/issues/show_bug.cgi?id=1861
> 
> This issue will take you on a guided tour of _all_ the Subversion 
> libraries, but you will not have to confront the darker magic dwelling 
> in them. After your tour is complete, you will send a patch to the dev@ 
> list; if it is accepted (there has to be /some/ kind of exit exam), you 
> will be counted among the contributers to Subversion 1.1.
> 
> Are you up to the challenge! Click the link today!
> 
> -- Brane
> 
> /me doesn't mention that fact that it's brain-dead, but necessary work 
> he wants to fob off on some willing victim :-)

I'm happy to do it, but it might be a 48-hour job... meaning I've got an 
exam tomorrow.

<quote>
Now that the version query/check infrastructure is in the code, we 
should add

a) Version query functions to all svn libraries;
    see include/svn_client.h, libsvn_client/version.c

b) Version checks to all command-line clients;
    see clients/cmdline/main.c:check_lib_versions
</quote>

I take it it's just a) duplicating the version changes to libsvn_client 
to the other libraries (with appropriate naming); and b) duplicating 
clients/cmdline/main.c:check_lib_versions() to svnadmin, svnlook, 
svninfo, svndumpfilter, svnversion (with appropriate lists of libraries)?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org