"Files" <files@poetryunlimited.com> writes:
> Ben,
>
> Much much much clearer. Thank you. I guess not having worked with
> something as powerful as subversion, it makes it easy to fall into
> older patterns.
Well, really the problems here are that 1) you've not used Subversion
very much (personally), 2) you've not watched the development list,
and thus have no feel for this project's standard practices and
procedures... yet.
Usually, when we grant partial commit-access to somebody, they've
already had time to absorb the culture of our project. Hence the
misunderstandings.
> I really appreciate your candor. Can you tell me a good way to keep
> a maintain local versions while I'm making these changes so I can
> backtrack w/o impacting anyone?
Here's the question: go back and look at every single commit that you
made in the last couple of days. Is every change a *real* milestone?
Do *each* one of those commits represent a tree-state important enough
that you might want to "roll back" to it? I'd be surprised if you
said "yes"... and that's what I mean when I talk about increasing the
granularity of your commits.
> I guess I'm concerned about setting up a private repository and I'm
> wondering if there are any issues I should be aware of.
There's no such thing as a 'private' repository. This isn't a
decentralized system like arch or bitkeeper; you can't just randomly
synchronize a graph of independent repositories. All you can do is
maintain multiple private working-copies (branches), and keep a bunch
of patchfiles around ('svn diff > change1.patch').
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 23 16:40:41 2003