From: Linus Torvalds <torvalds@osdl.org>
To: Rob Landley <rob@landley.net>
Cc: git@vger.kernel.org
Subject: Re: Who do I report bugs in the git source web browser thing to?
Date: Thu, 23 Mar 2006 09:03:25 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0603230856250.26286@g5.osdl.org> (raw)
In-Reply-To: <200603231143.17762.rob@landley.net>
On Thu, 23 Mar 2006, Rob Landley wrote:
>
> When I go to kernel.org, click the tiny C next to linus's name to get the git
> browser for the tree, click "tree", click the "usr" directory, and then click
> "history" next to the file gen_init_cpio.c, it says this file appeared out of
> thin air 59 minutes ago.
It does?
For me, it says that the file has no history at all. Which is true. It
hasn't been changed since it was imported, and normally git doesn't show
the root commit at all (exactly because it's the "import" commit).
Now, gitweb _could_ use the "--root" flag to git-diff-tree to also show
the root commit as a diff against nothingness, and then each file would
always have at least _one_ history entry, but if you want that, you might
as well just click the "blob" button instead, that shows what the file is.
The one commit you see (the "[PATCH] reduce size of bio mempools" thing in
the header at the thing) is _not_ part of the file history: it's your
starting point for history searching. In other words, it's the top commit
that you do your history _off_.
Pick another file, like the Makefile, to see what real history looks like
(or, better yet, go into a different directory that actually sees more
real work, like kernel/, and look at the history of files there).
Linus
next prev parent reply other threads:[~2006-03-23 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 16:43 Who do I report bugs in the git source web browser thing to? Rob Landley
2006-03-23 16:51 ` Josh Boyer
2006-03-23 17:03 ` Linus Torvalds [this message]
2006-03-23 22:47 ` Rob Landley
[not found] ` <20060323182336.062fc63a.seanlkml@sympatico.ca>
2006-03-23 23:23 ` sean
2006-03-24 3:06 ` Rob Landley
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=Pine.LNX.4.64.0603230856250.26286@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=rob@landley.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 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).