Building a tool to make the process automated

[Ken Bloom]

On Tuesday 12 June 2007 05:09:40 pm Martin Fick wrote:
> Lastly, I have a conceptual enhancement for the
> svnauto tool that I have been thinking about for a
> while, maybe something that you want to consider for
> your project also.  The problem: I have directories
> that I do not want autoversioned, say a source code
> directory for which I want each commit to be a manual
> commit with a normal developer's commit message.  But
> within these directories I still want the safety of an
> autoversioning system!
>
> The solutions I can think of involve copying the
> unversioned (or changed but not checked in files) to a
> hidden subdirectory which can then be autoversioned
> into a separate junk repository.  I don't care if the
> junk repository fills up, the goal is to prune it
> often.  If later a file that was unversioned in the
> primary repository gets added to the primary repo, it
> will get deleted from the junk repo, (potentially this
> would be a good time to actually prune it from the
> junk repo?)  When I get more time to think about this
> idea I will add a proposal to the wiki.

It's possible that this is easier to do with a distributed version 
control system, like git or svk or ... the list goes on.


-- 
Ken Bloom. PhD candidate. Linguistic Cognition Laboratory.
Department of Computer Science. Illinois Institute of Technology.
http://www.iit.edu/~kbloom1/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.madduck.net/pipermail/vcs-home/attachments/20070612/6352bcf3/attachment.pgp>