From: Jakub Narebski <jnareb@gmail.com>
To: "Tarmigan Casebolt" <tarmigan@gmail.com>
Cc: "Junio C Hamano" <junkio@cox.net>,
git@vger.kernel.org,
"John 'Warthog9' Hawley" <warthog19@eaglescrag.net>
Subject: Re: gitweb bug?
Date: Tue, 26 Jun 2007 02:05:48 +0200 [thread overview]
Message-ID: <200706260205.49337.jnareb@gmail.com> (raw)
In-Reply-To: <905315640706242315v3f649ef5w2a0706d0c4c68d8e@mail.gmail.com>
On Mon, 25 June 2007, Tarmigan Casebolt wrote:
>
> I was looking through the kernel source and noticed a difference
> between the git version and the gitweb version here:
> http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=net/netlink
> on gitweb, I only see 4 files, but in git locally on linux I see 71.
>
> This might be because there are files that differ only in case? (I'm
> using OSX, which has problems with case, and in particular that
> directory of the kernel source.)
>
> Am I missing something, or is this a bug?
First of all, this question should be asked IMVHO on git mailing list,
with Cc: sent to Kernel.Org admins or John 'Warthog9' Hawley, author of
the gitweb modification (caching gitweb) used at kernel.org
I cannot help you what the contents of net/netlink should look like,
because I don't have clone of the linux kernel repository. By "in git
locally on linux" you mean in the working area? Or perhaps result of
"git ls-tree HEAD:net/netlink"? You should have provided command used
to get those 71 files, and perhaps even those 71 files list.
--
Jakub Narebski
Poland
next parent reply other threads:[~2007-06-25 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <905315640706242315v3f649ef5w2a0706d0c4c68d8e@mail.gmail.com>
2007-06-26 0:05 ` Jakub Narebski [this message]
2007-06-26 5:14 ` gitweb bug? J.H.
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=200706260205.49337.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=tarmigan@gmail.com \
--cc=warthog19@eaglescrag.net \
/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.