[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] [BUG] Re: patch logs not rfc(2)822 compatible]
From: |
Bug Goo |
Subject: |
Re: [Gnu-arch-users] [BUG] Re: patch logs not rfc(2)822 compatible] |
Date: |
Fri, 28 May 2004 15:01:09 +0000 |
Created as bug 133
On Thu May 27 20:37:31 2004, Tom Lord wrote:
>
>
> ------- Start of forwarded message -------
> X-Injected-Via-Gmane: http://gmane.org/
> To: address@hidden
> From: Matthew Dempsky <address@hidden>
> Date: Wed, 26 May 2004 11:15:54 -0500
> Content-Type: text/plain; charset=us-ascii; format=flowed
> X-Complaints-To: address@hidden
> X-Gmane-NNTP-Posting-Host: hostr675e.alcatel.com
> User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
> X-Accept-Language: en-us, en
> In-Reply-To: <address@hidden>
> Subject: [Gnu-arch-users] Re: patch logs not rfc(2)822 compatible
> X-BeenThere: address@hidden
> X-Mailman-Version: 2.1.4
> Precedence: list
> List-Id: a discussion list for all things arch-ish <gnu-arch-users.gnu.org>
> List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/gnu-arch-users>,
> <mailto:address@hidden>
> List-Archive: <http://mail.gnu.org/pipermail/gnu-arch-users>
> List-Post: <mailto:address@hidden>
> List-Help: <mailto:address@hidden>
> List-Subscribe: <http://mail.gnu.org/mailman/listinfo/gnu-arch-users>,
> <mailto:address@hidden>
> Sender: address@hidden
> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail.42inc.com
> X-Spam-DCC: SdV: mail 1179; Body=2 Fuz1=2 Fuz2=2
> X-Spam-Status: No, hits=-1.0 required=4.5 tests=BAYES_00 autolearn=ham
> version=2.63
> X-42email-MailScanner-Information: Please contact
> http://www.42inc.com/support.html for more information.
> X-42email-MailScanner: Found to be clean
> X-UIDL: 67955b2b76491c10e245498a04c4580e
>
>
> Miles Bader wrote:
>
> > To the best of my knowledge, it's not really intended to be parsable -- it's
> > just a string.
>
> I think you may misunderstand the issue -- you're right that tla never
> uses the Date entry in the patch logs (instead it uses Standard-date),
> however, RFC 822 reserves Date as a header entry and also specifies the
> formatting it uses. Consequently, attempting to use a strict RFC 822
> parser to load a patch log will error when it finds the bad header entry.
>
> Since tla doesn't need to read (well, parse at least) the Date header
> entry back in, I think we'd be fine simply changing the output format.
> Only scripts that rely on it being non-RFC-822-compliant will break.
>
> - -jivera
>
>
>
> _______________________________________________
> Gnu-arch-users mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gnu-arch-users
>
> GNU arch home page:
> http://savannah.gnu.org/projects/gnu-arch/
> ------- End of forwarded message -------
>
>
> _______________________________________________
> Gnu-arch-users mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gnu-arch-users
>
> GNU arch home page:
> http://savannah.gnu.org/projects/gnu-arch/
>