[sldev] LSL SVN

[Erik Anderson]

The thing is, I've had people do plenty of work "outside of their SVN
directory", copying in changes when they're ready to commit them.  Then I
usually have to take the time to go through their diffs and try to figure
out which changes they intended and which ones they overwrote/rolled back
accidentally by copying stuff in.  SVN is intended to have their working
directories be the primary development point, anything else and you start
getting into dangerous and frustrating confusion.

On 10/31/07, Argent Stonecutter <secret.argent at gmail.com> wrote:
>
> I think SVN or CVS support would be great, but they wouldn't need to
> be built in to the client.
>
> I'd be happy if it would just:
>
> 1. Have a "File->Save" option to let me save the script I'm editing
> to (say) "~/Scripts/Cyberflight.lsl"
> 2. Have a "File->Load" option to let me load "~/Scripts/
> Cyberflight.lsl" into the script I'm editing.
>
> Plus...
>
> 3. Periodically save the script to a file in "~/Scripts/
> Cyberflight.lsl.bak", or maybe "~/Scripts/Flight Feather/Cyberflight
> 1.4.3.bak".
> 4. Also save it to the .bak file when I save the script, or when the
> client quits with a script editor window open.
>
> Then I could maintain the LSL code in my own source control system of
> choice, and I wouldn't lose everything I'd done if the asset server
> is being an ass. Of course, the "autosave file" name should not be
> the same as the name of the file I loaded the script from.
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20071031/f4333998/attachment-0001.htm