Building a tool to make the process automated
mogulguy at yahoo.com
Wed Jun 13 04:47:23 CEST 2007
--- Ken Bloom <kbloom at gmail.com> wrote:
> On Tuesday 12 June 2007 05:09:40 pm Martin Fick
> > 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
> > your project also. The problem: I have
> > that I do not want autoversioned, say a source
> > directory for which I want each commit to be a
> > commit with a normal developer's commit message.
> > 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
> > into a separate junk repository. I don't care if
> > junk repository fills up, the goal is to prune it
> > often. If later a file that was unversioned in
> > primary repository gets added to the primary repo,
> > will get deleted from the junk repo, (potentially
> > would be a good time to actually prune it from the
> > junk repo?) When I get more time to think about
> > 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.
Could you elaborate on what you mean here, I'm not
sure I am familiar enough with their featuresets to
understand how they would do this.
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
More information about the vcs-home