Because my team is not as eager as I am to jump in with subversion,
I'm trying to think of a way I could begin using it to manage my own
contributions without their immediate participation.
Currently, we all work out of a shared directory, making local copies
of files we're working on, then copying those back to the server. My
first thought was to import the current project from the server into
my own repository, then (secretly!) replace that tree on the server
with a checked-out copy. From then on, I'd make my own changes as if
the project was officially versioned, and then I'd go to the server
and run an svn update. To bring their changes into my repository, I'd
sneak over and make one big commit each night, with a message to the
effect of "Everyone else's changes."
I know that if I can show how the immediate benefits of version
control are available with minimal fuss, everyone will join in right
away. In the meantime, I want the benefits for my own sake, and the
demonstration of the viability will really help my pitch in the
coming months.
So... those of you with a mischievous streak... should I go for it?
j
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 4 01:41:46 2005