From: Kay Sievers <kay.sievers@vrfy.org>
To: Ismail Donmez <ismail@uludag.org.tr>
Cc: git@vger.kernel.org
Subject: Re: Rss produced by git is not valid xml?
Date: Fri, 18 Nov 2005 21:02:17 +0100 [thread overview]
Message-ID: <20051118200217.GA2831@vrfy.org> (raw)
In-Reply-To: <200511182127.06958.ismail@uludag.org.tr>
On Fri, Nov 18, 2005 at 09:27:06PM +0200, Ismail Donmez wrote:
> On Friday 18 November 2005 19:26, you wrote:
> > On Friday 18 November 2005 18:33, you wrote:
> > > Hi all,
> > >
> > > I am trying to parse git's rss feed and now xml parsers seems to choke on
> > > it because of an error in the produced feed. Looking at
> > > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=rs
> > >s
> > >
> > > line 781 says :
> > >
> > > On Thu, 17 Nov 2005, David G\363mez wrote:<br/>
> > >
> > > which is part of the commit :
> > > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=co
> > >mm it;h=05b8b0fafd4cac75d205ecd5ad40992e2cc5934d
> >
> > Ok looks like this text is latin-1 encoded although xml is served as utf-8.
>
> Any comments on this?
Yes, convince the git maintainers, that it's incredibly stupid not to
enforce utf8 in commit messages. It makes absolutely zero sense in a
SCM, which merges forth and back between people around the world to
allow random encodings from the last century.
I still can't believe that this is a subject for discussion, in a
software developed in the year 2005.
With the next round of gitweb, I will substitute these caracters with
valid utf8, which will show up as invalid chars.
And git guys, please start to think again about your insane options,
that cause more harm than anything good.
Thanks,
Kay
next prev parent reply other threads:[~2005-11-18 20:02 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 16:33 Rss produced by git is not valid xml? Ismail Donmez
2005-11-18 17:26 ` Ismail Donmez
2005-11-18 19:27 ` Ismail Donmez
2005-11-18 20:02 ` Kay Sievers [this message]
2005-11-18 20:08 ` Ismail Donmez
2005-11-18 20:22 ` Linus Torvalds
2005-11-18 20:28 ` H. Peter Anvin
2005-11-18 20:47 ` Linus Torvalds
2005-11-18 20:55 ` H. Peter Anvin
2005-11-18 20:51 ` Josef Weidendorfer
2005-11-18 21:01 ` Kay Sievers
2005-11-18 20:45 ` Ismail Donmez
2005-11-18 21:13 ` Linus Torvalds
2005-11-18 21:22 ` Ismail Donmez
2005-11-18 21:25 ` Junio C Hamano
2005-11-18 21:29 ` Ismail Donmez
2005-11-19 8:48 ` Junio C Hamano
2005-11-18 20:55 ` Kay Sievers
2005-11-18 21:30 ` Linus Torvalds
2005-11-18 21:33 ` Ismail Donmez
2005-11-18 21:48 ` Linus Torvalds
2005-11-18 22:12 ` H. Peter Anvin
2005-11-18 23:20 ` Linus Torvalds
2005-11-18 23:34 ` H. Peter Anvin
2005-11-18 23:53 ` Andreas Ericsson
2005-11-19 1:22 ` H. Peter Anvin
2005-11-19 8:49 ` Andreas Ericsson
2005-11-19 10:58 ` Johannes Schindelin
2005-11-18 23:57 ` Linus Torvalds
2005-11-18 23:58 ` H. Peter Anvin
2005-11-19 0:29 ` Johannes Schindelin
2005-11-18 23:25 ` Linus Torvalds
2005-11-19 0:34 ` Johannes Schindelin
2005-11-19 0:37 ` Junio C Hamano
2005-11-19 1:05 ` Linus Torvalds
2005-11-19 10:31 ` Junio C Hamano
2005-11-19 17:52 ` Linus Torvalds
2005-11-20 1:16 ` Johannes Schindelin
2005-11-20 3:10 ` Linus Torvalds
2005-11-20 4:13 ` Johannes Schindelin
[not found] ` <20051127025249.GA12286@vrfy.org>
2005-11-27 3:57 ` Junio C Hamano
2005-11-27 4:13 ` Linus Torvalds
2005-11-28 0:39 ` [PATCH 2/3] mailinfo: allow -u to fall back on latin1 to utf8 conversion Junio C Hamano
2005-11-28 6:32 ` H. Peter Anvin
2005-11-28 9:21 ` Junio C Hamano
2005-11-27 16:18 ` Rss produced by git is not valid xml? Kay Sievers
2005-11-19 0:04 ` Johannes Schindelin
2005-11-20 18:28 ` H. Peter Anvin
2005-11-21 8:38 ` Johannes Schindelin
2005-11-21 9:28 ` H. Peter Anvin
2005-11-19 3:28 ` Junio C Hamano
2005-11-19 4:35 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2005-11-19 6:31 Marco Costalba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051118200217.GA2831@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=git@vger.kernel.org \
--cc=ismail@uludag.org.tr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).