Hi Ryan,
Thanks,
The idea is to resolve the issues in subversion.
1. Always update from server .
2. Always lock the file.
3. Always checkin the file.
This is the small rapper so It will take care of update, lock and checkin.
You can remove the diff option as per your requirement.
Regards,
Mike
http://forum.opensourcedevelopment.net
Ryan Schmidt <subversion-2007b@ryandesign.com> wrote:
On Sep 1, 2007, at 06:01, mic_linux_USA mic_linux_USA wrote:
> Most of the time developers forget to checkin or update the file/
> folders from server,
Then you have an education problem among your developers. You should
be fixing that problem by educating your developers on the proper use
of a revision control system, not creating scripts to support their
ignorance. All developers using Subversion should be encouraged to
read as much of the book as possible: http://svnbook.org/ (or other
books on the topic of Subversion -- there are versions in other
languages as well in case that's helpful)
> With this bash script file will automatically update from server,
> then lock and open in vi editor whenever developer save the file it
> will ask for commit message and checkin in server after that it
> will unlock for other developers.
>
> Please copy the script from http://opensourcedevelopment.net/text-
> tutorials/subversion-six-commands-in-one-script.html
It's pretty common to need to change multiple files in order to
effect a particular change. Your script seems to encourage committing
after changing each file. That's probably a bad idea.
It's also pretty silly to offer an option to use set the log message
of a commit to the diff of the commit.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------
Be a better Globetrotter. Get better travel answers from someone who knows.
Yahoo! Answers - Check it out.
Received on Sun Sep 2 04:46:30 2007