I'd suggest to tag the trunk when stabilizing for a release. Then work
directly on the tag to stabilize and merge patches back to the trunk. That
way trunk development does not have to stop while wrapping up the last
issues for the release.
regards,
Freyr
On Dec 30, 2007 10:15 PM, Bruce Markham <[EMAIL PROTECTED]> wrote:
> Having no experience with the command-line subversion tool, I can't seem
> to lock anything from work. If I target the repo, its says that I need to
> target a file. And if I target my local working copy, it says that it isn't
> a working copy. (I suspect again that it means I have to do a file-by-file
> lock.)
>
> I'll still try to do as much cleanup as I can. But deity forbid anyone
> from screwing me up.... so... no commits folks, for 8 hours. No commits.
> Capisce?
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> SharpOS-Developers mailing list
> SharpOS-Developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sharpos-developers
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
