|
From: <sv...@va...> - 2005-05-31 21:33:21
|
Author: rjwalsh Date: 2005-05-31 22:33:15 +0100 (Tue, 31 May 2005) New Revision: 120 Modified: trunk/index.html Log: Minor white-space only thing to test my password. Modified: trunk/index.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/index.html 2005-05-21 19:24:10 UTC (rev 119) +++ trunk/index.html 2005-05-31 21:33:15 UTC (rev 120) @@ -9,7 +9,6 @@ Current stable release: <a href=3D"/downloads/source_code.html#current-s= table"><?php echo $config['release-version']; ?></a> </h3> =20 - <p> </p> =20 <p>Valgrind is an <a href=3D"http://opensource.org/OSA/">award-winning</= a>=20 |
|
From: Nicholas N. <nj...@cs...> - 2005-05-31 21:43:50
|
On Tue, 31 May 2005 sv...@va... wrote: > Modified: trunk/index.html > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- trunk/index.html 2005-05-21 19:24:10 UTC (rev 119) > +++ trunk/index.html 2005-05-31 21:33:15 UTC (rev 120) > @@ -9,7 +9,6 @@ > Current stable release: <a href=3D"/downloads/source_code.html#current-s= > table"><?php echo $config['release-version']; ?></a> > </h3> > =20 > - > <p> </p> > =20 > <p>Valgrind is an <a href=3D"http://opensource.org/OSA/">award-winning</= > a>=20 Here's a question: in my mailer these commit messages always look a bit funny. I don't know if you can see it above, but the line after the "Modified" line has lots of "=3D" strings in a row. I think it's just meant to be '=' characters. And some of the lines further down have "=20" as their last character. Does anyone else see this? Any ideas how to fix it? Nick |
|
From: Robert W. <rj...@du...> - 2005-05-31 21:52:21
|
> Here's a question: in my mailer these commit messages always look a bit > funny. I don't know if you can see it above, but the line after the > "Modified" line has lots of "=3D" strings in a row. I think it's just meant > to be '=' characters. And some of the lines further down have "=20" as > their last character. > > Does anyone else see this? Any ideas how to fix it? Those are, I believe, special magic mime encodings for whitespace, = and the like. I don't see them, which means my mailer (Evolution) is decoding them correctly. What's your mailer? Is it mime-aware? Regards, Robert. |
|
From: Nicholas N. <nj...@cs...> - 2005-05-31 22:34:53
|
On Tue, 31 May 2005, Robert Walsh wrote: > Those are, I believe, special magic mime encodings for whitespace, = and > the like. I don't see them, which means my mailer (Evolution) is > decoding them correctly. What's your mailer? Is it mime-aware? Pine (advance, I know). I think it's MIME-aware... it can handle multi-part MIME messages, at least. Nick |
|
From: Greg P. <gp...@us...> - 2005-05-31 22:21:40
|
Nicholas Nethercote writes:
> Here's a question: in my mailer these commit messages always look a bit
> funny. I don't know if you can see it above, but the line after the
> "Modified" line has lots of "=3D" strings in a row. I think it's just meant
> to be '=' characters. And some of the lines further down have "=20" as
> their last character.
This is MIME quoted-printable text encoding. You should see
Content-Transfer-Encoding: quoted-printable
in the original message's headers.
=3D is the equals sign. =20 is a space, usually at the end of a line.
> Does anyone else see this? Any ideas how to fix it?
A sufficiently sophisticated mail reader should be able to display
quoted-printable text as something more readable. The only other
alternative is to change the message encoding used when the svn
system generates the message.
--
Greg Parker gp...@us...
|
|
From: Greg P. <gp...@us...> - 2005-05-31 22:41:06
|
Greg Parker writes: > A sufficiently sophisticated mail reader should be able to display > quoted-printable text as something more readable. The only other > alternative is to change the message encoding used when the svn > system generates the message. The problem is that the original message does not include a MIME-Version header. Any message that specifies a Content-Transfer-Encoding must also include MIME-Version. This is probably a bug in the generator of the message. I'm guessing that some mail clients enforce the letter of the law and ignore Content-Transfer-Encoding when no MIME-Version is present. -- Greg Parker gp...@us... |
|
From: Nicholas N. <nj...@cs...> - 2005-05-31 22:55:44
|
On Tue, 31 May 2005, Greg Parker wrote: > The problem is that the original message does not include > a MIME-Version header. Any message that specifies a > Content-Transfer-Encoding must also include MIME-Version. > This is probably a bug in the generator of the message. > I'm guessing that some mail clients enforce the letter of > the law and ignore Content-Transfer-Encoding when no > MIME-Version is present. Ah, you're exactly right: I added the Mime version line and Pine displayed it properly. Thanks, Greg. So the follow-up question: how do we make Subversion include the Mime version line? N |
|
From: Cerion Armour-B. <ce...@op...> - 2005-06-01 11:04:23
|
On Wednesday 01 June 2005 00:55, Nicholas Nethercote wrote: > So the follow-up question: how do we make Subversion include the Mime > version line? Added the line to the post-commit hook commit-email.pl C. |
|
From: Nicholas N. <nj...@cs...> - 2005-06-01 18:13:03
|
On Wed, 1 Jun 2005, Cerion Armour-Brown wrote: > On Wednesday 01 June 2005 00:55, Nicholas Nethercote wrote: >> So the follow-up question: how do we make Subversion include the Mime >> version line? > > Added the line to the post-commit hook commit-email.pl It works! Thanks. N |