From: Linus Torvalds <torvalds@osdl.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: latest blob date (request)
Date: Mon, 16 Jan 2006 11:00:33 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0601161055300.13339@g5.osdl.org> (raw)
In-Reply-To: <20060115173100.1134256b.rdunlap@xenotime.net>
On Sun, 15 Jan 2006, Randy.Dunlap wrote:
>
> I would find it helpful (a user optimization) if each tree list
> contained a date-last-modified/updated. This could be used
> to help decide if I (someone) wanted to click on a particular
> blob or history (OK, blobs are quick, but history can be
> very time-consuming, so being able to shortcut or skip
> history would be very helpful IMO).
That's fundamentally a very expensive operation in git.
A "blob" doesn't have a date - and indeed, it cannot have one, since the
same blob may be associated with multiple different pathnames, and
multiple different commits.
If you have a particular pathname, you can ask "when was this pathname
changed last", which is basically
git-rev-list --max-count=1 HEAD -- Makefile
but that's not very cheap either.
Linus
prev parent reply other threads:[~2006-01-16 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 1:31 latest blob date (request) Randy.Dunlap
2006-01-16 5:07 ` Paul Mackerras
2006-01-16 5:10 ` gitweb: " Randy.Dunlap
2006-01-16 17:44 ` Kay Sievers
2006-01-16 17:46 ` Randy.Dunlap
2006-01-16 17:55 ` Junio C Hamano
2006-01-16 19:00 ` Linus Torvalds [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=Pine.LNX.4.64.0601161055300.13339@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=rdunlap@xenotime.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).