I looked at bug ID 908, which wants that the local copy in text-base
should be stored compressed. I did a little digging around in code and
felt it shouldnt be very hard to implement this and it will atleast
make my life easier.
I am not going through the Google summer of code thing (am no longer a
student either :-) but would like to implement this feature (assuming
someone hasnt already started working on this).
I am a long time subversion user (on Windows, TortoiseSVN) but new to
subversion code, so will need some guidance if you guys want me to
work on this.
Some quick quesitions:
# Is libsvn_wc/ the only place where I will need to edit code, or do I
need to look in other directories too? Which ones?
# Do we already have a compression library (zlib?) linked in subversion?
# How much additional delay this is expected to result in during
checkouts and commits? Should I use something lightweight like zlib or
will it be fine to use bzip2 which can give better compression but
will be slower?
# Do we want files in text-base to be always compressed, or do we want
text-base compression to be optional?
Bug no 525 (optional text-base storage) is slightly related, maybe I
can have a design which will make it easier to implement 525 too. Like
implementing text-base access as a layer which can have multiple
implmentations:
1. Direct file read
2. Read compressed file
3. Fetch from server
Another possible todo item (which runs in opposite direction from the
above items :-)
Just like SVN stores text-base for local diffs, how about generalizing
it to store N previous revisions and change log entires. Storing
additional revisions shouldn't result in too much bloat, as we can
probably store just the diffs and can make more operations local.
Sachin Garg [India]
www.sachingarg.com | www.c10n.info
On 5/7/06, David Anderson <david.anderson@calixo.net> wrote:
> Just a quick reminder, as it has been all over the internet for some
> time.
>
> Following last year's success, Google is hosting a 2006 edition of the
> Summer of Code. Quickly put, if you're a student and get selected,
> you get paid over the summer to work on a specific task within one of
> dozens of mentoring open source projects. More information about the
> specifics of the program are available at http://code.google.com/soc/ .
>
> Like last year, Subversion is a mentoring organization within the SoC.
> If you'd like to help further the development of Subversion, get paid,
> and have fun doing so, then head over to the SoC webpage and apply!
>
> We have compiled a list of tasks that we feel are suitable for the
> timeframe of the SoC and interesting to us. The list is on the
> Subversion website, at
> <http://subversion.tigris.org/project_tasks.html>. This list is of
> course not exhaustive, so if you have a really great idea that might
> interest us, don't let our list stop you from applying.
>
> The deadline for applying is 8th May. Yes it is soon, but it should
> be enough to decide what you want to apply for, and write a short
> proposal for it. Remember, the application is meant to interest us in
> the task you're offering to complete, and convince us that you are
> able to complete the task you propose.
>
> No need to have finished the task beforehand, or have the deepest
> possible knowledge of the Subversion internals before starting. Some
> coding skills, along with a keen will to learn should do the trick!
>
> - Dave.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 8 10:33:34 2006