Re: white-space & line-ending changes

2002-12-02 Thread Oleg Tkachenko
J.Pietschmann wrote: I had the same problem when I commited for the first time. As far as I found out, you have to be subscribed to fop-cvs mail list using your *apache email address* + first message may be postponed a little bit by moderator (nobody knows who is it though :). BTW I'm subscr

RE: white-space & line-ending changes

2002-12-01 Thread Victor Mote
J.Pietschmann wrote: > Well, the cvs commit command has to be invoked from within the checked out > tree. Otherwise no commit message is mailed at all. > For example > $pwd > $CWD is /usr/pietsch/gnu/fop > $cvs checkout xml-fop > $... > Change to xml-fop before committing at this place. > $ cd xml

Re: white-space & line-ending changes

2002-12-01 Thread J.Pietschmann
Oleg Tkachenko wrote: Victor Mote wrote: I have committed some changes to the trunk that clean up 1) tabs, 2) spaces at end of lines, and 3) CR/LF line endings. These touched quite a few files, mostly doc, but should have no effect other than to minimize future spurious deltas. I do not see t

Re: white-space & line-ending changes

2002-11-30 Thread Oleg Tkachenko
Victor Mote wrote: I have committed some changes to the trunk that clean up 1) tabs, 2) spaces at end of lines, and 3) CR/LF line endings. These touched quite a few files, mostly doc, but should have no effect other than to minimize future spurious deltas. I do not see the auto mail messages comin

white-space & line-ending changes

2002-11-30 Thread Victor Mote
I have committed some changes to the trunk that clean up 1) tabs, 2) spaces at end of lines, and 3) CR/LF line endings. These touched quite a few files, mostly doc, but should have no effect other than to minimize future spurious deltas. I do not see the auto mail messages coming from CVS related t