linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Michael Krufky <mkrufky@m1k.net>
Cc: webmaster@kernel.org, lkml <linux-kernel@vger.kernel.org>,
	Michael Krufky <mkrufky@gmail.com>
Subject: Re: [KORG] GITWEB doesn't show any DIFF's
Date: Tue, 17 Jan 2006 17:39:17 +0000	[thread overview]
Message-ID: <200601171739.17168.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <43CCF8BB.1050009@m1k.net>

On Tuesday 17 January 2006 14:01, Michael Krufky wrote:
> To Whom (and ALL) that it may concern:
>
> For the past week or so, I haven't been able to get gitweb, running on
> kernel.org, to show me any diff's.
>
> For each commit, if I click on the "commit" link, or "commitdiff" link,
> the best I get is something that looks like this:
>
> file:fd8bc718f0e33df0a446d3d5c67f68929eca6490
> <http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blo
>b;h=fd8bc718f0e33df0a446d3d5c67f68929eca6490;hb=e0ad8486266c3415ab9c17f5c03c
>47edc7b93d7b;f=drivers/media/video/cx88/cx88-alsa.c> ->
> file:e649f678d47ab0a749b89146867ff9b1f513f73a
> <http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blo
>b;h=e649f678d47ab0a749b89146867ff9b1f513f73a;hb=e0ad8486266c3415ab9c17f5c03c
>47edc7b93d7b;f=drivers/media/video/cx88/cx88-alsa.c>
>
> This is for "V4L/DVB (3375): git dvb callbacks fix" , but it happens for
> every patch I try to view...  Even if I try to view the patch in "plan"
> mode, the following is all that I can see:
>
> From: Andrew Morton <akpm@osdl.org>
> Date: Sun, 15 Jan 2006 08:45:20 +0000 (-0200)
> Subject: V4L/DVB (3375): git dvb callbacks fix
> X-Git-Tag: v2.6.16-rc1
> X-Git-Url:
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm
>itdiff;h=e0ad8486266c3415ab9c17f5c03c47edc7b93d7b
>
> V4L/DVB (3375): git dvb callbacks fix
>
> - Not sure what went wrong here, but SND_PCI_PM_CALLBACKS got deleted.
>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@infradead.org>
> ---
>
> (I havent seen this patch, and I'm really curious what happens in it,
> and the explanation of the commit message -- these questions are
> probably answered simply by viewing the patch, which I cant do :-(  )
>
> ... I have tried this at multiple locations, using several different
> browsers under different OS's ... It won't show me a diff no matter what
> I do, and it USED to work (about a week ago)
>
> I'm surprised nobody has complained about this already.  (or maybe I
> just didnt see any such thread about it)

Seems to work for me right _now_, could you verify that this is still 
happening?

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2006-01-17 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 14:01 [KORG] GITWEB doesn't show any DIFF's Michael Krufky
2006-01-17 17:39 ` Alistair John Strachan [this message]
2006-01-17 17:52   ` Diego Calleja
2006-01-17 18:07     ` Jesper Juhl
2006-01-17 18:15       ` Michael Krufky
2006-01-17 17:59   ` Michael Krufky
2006-01-17 18:17     ` Alistair John Strachan
2006-01-17 18:27       ` Michael Krufky
2006-01-17 18:53         ` Nathan Laredo

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=200601171739.17168.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkrufky@gmail.com \
    --cc=mkrufky@m1k.net \
    --cc=webmaster@kernel.org \
    /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).