From: Jakub Narebski <jnareb@gmail.com>
To: "Lars Hjemli" <hjemli@gmail.com>
Cc: "Adam Mercer" <ramercer@gmail.com>, git@vger.kernel.org
Subject: Re: XML parsing error from gitweb at freedesktop.org
Date: Sat, 08 Dec 2007 02:49:44 -0800 (PST) [thread overview]
Message-ID: <m3d4thtqaq.fsf@roke.D-201> (raw)
In-Reply-To: <8c5c35580712061411k7a40a08el35f31c43add25cb3@mail.gmail.com>
"Lars Hjemli" <hjemli@gmail.com> writes:
> On Dec 6, 2007 10:34 PM, Adam Mercer <ramercer@gmail.com> wrote:
>>
>> as cgit displays the commit OK
>>
>> <http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.2-apple&id=48e6a75fbdd0fee86e364f02ace83f20b312a2b2>
>>
>> leads me to think that the problem lies in gitweb. Could this be a
>> problem with gitweb?
>>
>
> Actually, it's a problem in both cgit and gitweb, but you need to look
> a bit harder to find the error in cgit. It seems that gitweb on
> freedesktop.org doesn't detect a file rename (due to diff.renamelimit
> maybe?), so it shows the full source of the offending files, while in
> cgit you'll need to go from the diff to either the old or the new
> sourcefile to get the same error:
>
> http://cgit.freedesktop.org/xorg/xserver/tree/hw/darwin/quartz/applewmExt.h?h=xorg-server-1.2-apple&id=141f69dc3d8d6e7d8ff65607f43700ac11243041
> http://cgit.freedesktop.org/xorg/xserver/diff/hw/xquartz/applewm.c?h=xorg-server-1.2-apple&id=48e6a75fbdd0fee86e364f02ace83f20b312a2b2
>
> The problem is a number of unencoded ascii char 12.
Strange... I have checked gitweb code, and esc_html used in HTML
version of diff output escapes _all_ control characters ([:cntrl:]).
So ASCII char 12 should be shown as \014 in "cntrl" style.
Ahhh... I see, Freedesktop.org uses some ANCIENT version of gitweb,
from before it was included in git repository.
Try to ask Freedesktop.org admins to upgrade gitweb. Some nice
features include:
* mod_perl compatibility
* ability to display binary files correctly
* gitweb do not use /usr/bin/diff, and do not use temporary files
(and supports renames, typechanges and combined diff format)
* better support for strange characters in contents and in pathnames
* very basic support for submodules
* snapshot support (optional)
* forks support (optional)
* 'next' links in 'commit' and 'commitdiff' view
* optional features: commit search, pickaxe search, snapshots
support,...
--
Jakub Narebski
ShadeHawk on #git
prev parent reply other threads:[~2007-12-08 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 21:34 XML parsing error from gitweb at freedesktop.org Adam Mercer
2007-12-06 22:11 ` Lars Hjemli
2007-12-08 10:49 ` Jakub Narebski [this message]
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=m3d4thtqaq.fsf@roke.D-201 \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=ramercer@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.