Hi,
Ben suggested that I try here for an in-depth response to
my questions.
I am a graduate student at UCSC, and have been using subversion
since around revision 1100. As a class project, I would like
to do an initial pathfinding/feasibility study on adding
archiving of merge attributes (to Properties, as Ben mentioned
is planned) and possibly even previous conflict resolution data.
I'd like this to be something useful for the Subversion designers
as well. So, I'd like to ask if anyone familiar with the
issues would like to spend maybe 1-2 hours IRCing with me
over the next two weeks, to make sure that I produce something
you all would like to see. Any 30-second pointers to where I
should start examining the code will also be helpful, of course!
One main goal of this work is to maintain the overall design
goals built into Subversion; hence, the archiving of data
previously only available through controlled workspaces
(like conflict resolution activities, merge choices, etc.)
may have to be approached cautiously. Do we want users to
have to peform more steps for each merge done? Should
subversion only archive the data it can get without any more
user effort? I'll also need to know these sorts of constraints.
So, if anyone is interested in helping out with this project,
please let me know. My hours are fairly flexible and I can
probably work around your schedules, when live communication
is necessary.
Thanks,
Jennifer Bevan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 20 07:03:04 2003