Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Fri, 25 Mar 2005 16:33:44 +0000, Tony Hoyle <tmh at nodomain.org> wrote: >It'd be better on standard input... putting file lists on the command >line isn't going to work in the long term. If it's going to change, >better to change it completely... Right! >Import is just a large number of adds and updates in... It could be >treated as such rather than trying to make the same script do two >completely different things. That's fine with me. The only reason that I am doing detective work now is that there was no way to figure out stuff the same way since the messages on import differed. The revisions were nowhere to be seen too. Better to explicitly send them so there is no guesswork anymore. > >> Command line argument indicates the module, but there are no files. > >I'd have the same for commit. > >> Maybe adding a new marker called "Release:" will be possible: >> >> Modified Files: >> Tag: Module1 >> Release: Version6 >> FifthFile.txt,NONE,1.1.1.1 Fourth\ File.txt,NONE,1.1.1.1 >> SecondFile.txt,NONE,1.1.1.1 SixthFile.txt,1.1.1.1,1.1.1.2 >> ThirdFile.txt,1.1.1.2,1.1.1.3 >> >> What do you think? > >That would work, although I'd make it barer than that... > >Release:Version6 >Comment: >stuff > >A FifthFile.txt NONE 1.1.1.1 Module1 >A Fourth\ File.txt NONE 1.1.1.1 Module1 > >etc.. then it's relatively easily parsable. OK, a space separated list instead of a comma separated one, no big deal. But the A can be inferred from the revision, if the old rev is NONE then the file has been added. Branch tag on the end is fine too, in fact I have a parsing class that would be simpler if I don't have to remember stuff across the files. And one line per file maybe? Like shown above.... /Bo (Bo Berglund, developer in Sweden)