On Sat, Sep 5, 2009 at 9:00 PM, Heikki Johannes Junes<[email protected]> wrote: > $ svn checkout > http://${[email protected]/svnroot/rosegarden/trunk > trunk-rebasing > $ cd trunk-rebasing > $ svn move rosegarden/* ./ > $ svn move rosegarden/.*project ./ > $ svn move rosegarden/.settings ./
It would be better to do it by moving directories (as Michael noted) rather than files piecemeal. However, the real problem with this is that it would leave everyone who checked out trunk/ getting the website, old splash screens, etc., as well as the code. That's why we have trunk/rosegarden in the first place. To do this at all, if we were to have trunk/, branches/ and tags/ all as siblings (a convention, not a standard, btw), we would need to make them siblings under some other directory, with non-code stuff (stuff that does not get branched) as siblings to that other directory. If that makes any sense. I'm not inclined to comment much on the other garbage in this thread, but: Chris F., it's not all that intrusive to have to pause and do an svn switch before updating or committing, once only -- it shouldn't actually break anyone's working copy -- and Heikki: your rant was wholly inappropriate, this is not the case of an obviously superior technology being rejected on purely irrational grounds that you seem to think it is. That said, if we can improve things for everyone, that would be fine. Chris ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
