From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: 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 18:17:00 +0000 [thread overview]
Message-ID: <200601171817.00182.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <43CD309A.3030704@m1k.net>
On Tuesday 17 January 2006 17:59, Michael Krufky wrote:
[snip]
> >>
> >>... 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?
>
> I confirm, that nothing has changed...... Once again, no matter what OS,
> no matter what browser, no matter which location I am sitting at, I see
> no diff.
Try holding shift and pressing refresh. Maybe it's some bizarre caching issue?
Also, try s/www/zeus2/ in the URL to see if it's a problem specific to one
server (I wonder if the reason some of us have problems and others don't is
that we are being http load balanced).
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-01-17 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 14:01 Michael Krufky
2006-01-17 17:39 ` Alistair John Strachan
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 [this message]
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=200601171817.00182.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
all inboxes | Powered by JetHome®