Re: svnmucc
On 11/16/13 8:38 AM, Blair Zajac wrote: > The reason to support this syntax with command and arg on separate lines is to > support files with whitespaces in the names, which wouldn't be possible wit > the > syntax of command and arg on a single line. Yet another thing to add to the list of code that assumes that filenames don't have newlines in them.
Re: svnmucc
On 11/16/2013 03:06 AM, Andreas Mohr wrote: On Sat, Nov 16, 2013 at 04:29:13AM -0500, Geoff Rowell wrote: On Nov 16, 2013, at 2:10 AM, Vladislav Javadov wrote: rm programs/develop/fasm/tags rm programs/games/mine/tags rm programs/games/snake/tags Each command argument must be on a separate line: rm programs/develop/fasm/tags rm programs/games/mine/tags rm programs/games/snake/tags So, does that mean that svnmucc has single-arg support only? Cause given this example, on the syntax side there's nothing that would indicate that a new command is following, rather than further options to the existing command... (unless "rm" is one of the commands which are specially recognized as a known-supported command) Sorry for my critique (and thank you for your help!) - just sayin'... Not having looked at the source code, it probably just reads from the file until it reaches the end. The reason to support this syntax with command and arg on separate lines is to support files with whitespaces in the names, which wouldn't be possible wit the syntax of command and arg on a single line. Blair
Re: Migrating ClearCase data to Subversion
I've wound up doing a stack of source control migrations to SVN. I may be in a minority, but in general, *don't*. Do a flat export of the last timestamped copy, and add them to a Subversion tag in one step. Lock the tag, and then set a new trunk from that tag. This allows a number of very useful features: * Discard old material, especially with passwords or bulky binary images, before putting it in Subversion. Subversion does not support clearing out sensitive or inappropriately recorded data. * Update the layout first to Subversion's trunk, tags, and branches to create your new workflow. * Set the "svn:eol" and "svn:keywords" consistently at "add" time. You can then keep the old ClearCase server around, in read-only mode, if anyone feels a burning need for the old logs. But for most projects, preserving that amount of logs in the Subversion repository itself turns into a lot of engineering time better spent elsewhere. Note that this is *my* favored approach: others consider the old logs and layouts and individual merges to be vital and may have better suggests for keeping it. On Fri, Nov 15, 2013 at 5:47 PM, Olivier Antoine wrote: > Hi, > > I could not find a tool or an automated way to migrate ClearCase vobs to SVN > repositories. I guess there is not any perfect tool to do this. > > I don't think I can use timestamp to build revisions, like for migration cvs > to svn. > > On the other hand, the real need is to migrate main to trunk, to migrate the > other branches, probably just for the interesting file/directory versions - > the labelelled ones. I have to migrate the ClearCase labels to SVN tags. > I guess it is not possible to migrate the merge history. > > Could you help, please ? > > Olivier >
Re: svnmucc
> On Nov 16, 2013, at 6:06 AM, Andreas Mohr wrote: > >> On Sat, Nov 16, 2013 at 04:29:13AM -0500, Geoff Rowell wrote: >> >>> On Nov 16, 2013, at 2:10 AM, Vladislav Javadov wrote: >>> >>> rm programs/develop/fasm/tags >>> rm programs/games/mine/tags >>> rm programs/games/snake/tags >> >> Each command argument must be on a separate line: >> >> rm >> programs/develop/fasm/tags >> rm >> programs/games/mine/tags >> rm >> programs/games/snake/tags > > So, does that mean that svnmucc has single-arg support only? > Cause given this example, on the syntax side there's nothing > that would indicate that a new command is following, > rather than further options to the existing command... > (unless "rm" is one of the commands > which are specially recognized as a known-supported command) > > Sorry for my critique (and thank you for your help!) - just sayin'... > svnmucc commands have a fixed number of arguments. Use "svnmucc --help" to see the valid commands. - Geoff
Re: svnmucc
On Sat, Nov 16, 2013 at 04:29:13AM -0500, Geoff Rowell wrote: > > > On Nov 16, 2013, at 2:10 AM, Vladislav Javadov wrote: > > > > rm programs/develop/fasm/tags > > rm programs/games/mine/tags > > rm programs/games/snake/tags > > Each command argument must be on a separate line: > > rm > programs/develop/fasm/tags > rm > programs/games/mine/tags > rm > programs/games/snake/tags So, does that mean that svnmucc has single-arg support only? Cause given this example, on the syntax side there's nothing that would indicate that a new command is following, rather than further options to the existing command... (unless "rm" is one of the commands which are specially recognized as a known-supported command) Sorry for my critique (and thank you for your help!) - just sayin'... Andreas Mohr
Re: svnmucc
> On Nov 16, 2013, at 2:10 AM, Vladislav Javadov wrote: > > rm programs/develop/fasm/tags > rm programs/games/mine/tags > rm programs/games/snake/tags Each command argument must be on a separate line: rm programs/develop/fasm/tags rm programs/games/mine/tags rm programs/games/snake/tags - Geoff
