On Dienstag, 26. Juni 2007 Aaron Stone wrote: > Why do you want to upload one script and activate another one in one > shot? They're not logically related at all, so I don't want to > support that combination.
It was a mistake, it should have been 2 times the same name. I have no problem with mutual exclusive options, but that should a) be documented b) print an error so you can see it didn't pass Actually, the output looked as if there was no error, but neither the script was uploaded nor was the (other) script activated. There should be a clear indication that it didn't work out. We just finished our web interface for user administration. Users can select start/enddate, subject and text of a vacation, and we generate the script and upload it. A clear definition of how we could find out if the command was OK or not is definitely important :-) mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: EA39 8918 EDFF 0A68 ACFB 11B7 BA2D 060F 1C6F E6B0 // Keyserver: www.keyserver.net Key-ID: 1C6FE6B0
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
