white-space & line-ending changes

[Victor Mote <vi...@outfitr.com>]

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 to these
changes -- perhaps it is smart enough to know that these are innocuous, or
perhaps there is something wrong with my mail account. At any rate, I wanted
you to know what was going on when you see the files being updated.

Victor Mote


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: white-space & line-ending changes

[Oleg Tkachenko <ol...@multiconn.com>]

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 subscribed to fop-cvs with my spam-filtered address and have no
> problems.
But your commit messages nevertheless are sent only from pietsch@apache.org.
My conclusion was based on a quick analysis of $CVSROOT/CVSROOT/loginfo file 
at cvs.apache.org. This one usually defines an action being performed on each 
commit into a cvs repository. Our one runs $CVSROOT/CVSROOT/log_accum.pl 
script, which in turn (I should admit I'm not perl expert) actually 
consolidates message and sends it to the mail list through sendmail program 
from $ENV{'USER'}@apache.org address.
And if commit messages are always sent from $ENV{'USER'}@apache.org address, 
this one should be subscribed to the list.
May be there is another door though.

-- 
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

RE: white-space & line-ending changes

[Victor Mote <vi...@outfitr.com>]

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-fop
> $ cvs commit
> No parameters necessary. If the command asks you for a module to commit,
> or for logging in again, you made something wrong.
> BTW I'm subscribed to fop-cvs with my spam-filtered address and have no
> problems.

The commit was working, and I could even see that it was trying to create a
mail message -- it just wasn't getting mailed.

I followed Oleg's suggestion of switching my subscription to fop-cvs to my
apache.org mailing address & that seems to have fixed the problem. I am not
sure how to reconcile that with your experience -- maybe it just has to be
touched & maybe there is more than one way to do that. I guess I don't care
enough to find out. Thank you both for your help.

BTW, it is good to have you back.

Victor Mote


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: white-space & line-ending changes

["J.Pietschmann" <j3...@yahoo.de>]

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 the auto mail messages coming from CVS related to 
>> these
>> changes -- perhaps it is smart enough to know that these are 
>> innocuous, or
>> perhaps there is something wrong with my mail account. 
> 
> 
> 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 :).

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-fop
$ cvs commit
No parameters necessary. If the command asks you for a module to commit,
or for logging in again, you made something wrong.
BTW I'm subscribed to fop-cvs with my spam-filtered address and have no
problems.

J.Pietschmann


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: white-space & line-ending changes

[Oleg Tkachenko <ol...@multiconn.com>]

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 coming from CVS related to these
> changes -- perhaps it is smart enough to know that these are innocuous, or
> perhaps there is something wrong with my mail account. 

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 :).

-- 
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org