On Tue, May 21, 2013 at 1:13 PM, Andrew Reedick
<andrew.reed...@cbeyond.net> wrote:
>
> Right, right, it's the user's fault for failing to predict future "namespace"
> needs. That the repository was created when the project was small and that
> the user in question inherited the repo aren't valid excuses either.
Your bigger problem will come when you add enough projects that the
size of the repository becomes impractical to manage. Then it will be
your fault for not predicting the growth...
> Next time I'll implement top level directory changes via 'svnadmin dump/load'
> to avoid spurious log entries under branches/tags.
And you'll find that is less than perfect too if you want to extract
and move things that did not have stable parent paths.
> Translation: Les, that wasn't a very realistic or helpful piece of advice.
I'd call realizing that most software isn't perfect being realistic,
and learning to live with the imperfections to be more helpful than
waiting for everything to work the way you expect. Maybe in this
specific case some kind of event metadata could be added to note your
intent to create a branch or tag and that could be used instead of
--stop-on-copy to avoid confusing what you think of as tags and other
copies.
--
Les Mikesell
lesmikes...@gmail.com
