![]()
[<<]Message[>>] [<<]Author[>>] [<<]Subject [<<]Thread[>>]
Number : 4503 Date : 2003-05-02 Author : Kan Yabumoto Subject : Re: Date Macro Size(KB) : 1
DC: Yes, ultimate, we have to give in to the end user's "requirements" whether we agree or not. But, I strongly urge you to at least point out to the end users that it is a really bad idea to continue the m-d-yy scheme and tell them to consider changing their bad habit. As part of our efforts in making the ISO 8601 as wildly accepted standard as possible, we put extra efforts in making XXCOPY fully compatible with the ISO-8601. See my next message about the new version v.2.84.2. > Thanks for the fix. No, Please. We did not fix anything that was broken. We accommodated your (your end users') bad habit. It is an "enhancement" that in a way condones the bad practice and for that reason, we were reluctant to do so. (Luckily, the set of macro keywords had room to squeeze the notations without making it uglier). Kan Yabumoto =============================================================== At 2003-05-01 20:51, you wrote: >xxcopy c:\test d:\/$m-d-yy$ /tm-1 > >This works now. This is the base command without all the bells and >whistles. Basically I have to stay within a clients application >parameters. Their app uses date directory names without the padded >zeroes. I need to copy files from a central folder each evening >(after midnight) and get it into a directory dated from the day >before. I then also replicate the "day folders". Now my xxcopy >created folder will match their day folders and I will not have to >manually fix anything. > >Maybe I can finally roll this out to all the sites..... > >Thanks for the fix. > >DC
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.