Hi,
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).
--- ~Randy
Paul MackerrasRe: latest blob date (request)
Randy,
> 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).
Are you talking about gitk or gitweb? If you mean gitweb on kernel.org, Kay Sievers is who you need to talk to.
Paul.
gitweb: latest blob date (request)
On Mon, 16 Jan 2006 16:07:09 +1100 Paul Mackerras wrote:
> Randy, > > > 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). > > Are you talking about gitk or gitweb? If you mean gitweb on > kernel.org, Kay Sievers is who you need to talk to.
Sheesh, you are correct. Sorry.
Redirecting to Kay.
--- ~Randy
Re: gitweb: latest blob date (request)
On Sun, Jan 15, 2006 at 09:10:11PM -0800, Randy.Dunlap wrote:
> On Mon, 16 Jan 2006 16:07:09 +1100 Paul Mackerras wrote: > > > Randy, > > > > > 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). > > > > Are you talking about gitk or gitweb? If you mean gitweb on > > kernel.org, Kay Sievers is who you need to talk to. > > Sheesh, you are correct. Sorry.
Hmm, where do I find this information? It is recorded in last commit, that changed the file, right? I'm not sure, if we can get this out of the git tools?
Thanks, Kay
Re: gitweb: latest blob date (request)
On Mon, 16 Jan 2006, Kay Sievers wrote:
> On Sun, Jan 15, 2006 at 09:10:11PM -0800, Randy.Dunlap wrote: > > On Mon, 16 Jan 2006 16:07:09 +1100 Paul Mackerras wrote: > > > > > Randy, > > > > > > > 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). > > > > > > Are you talking about gitk or gitweb? If you mean gitweb on > > > kernel.org, Kay Sievers is who you need to talk to. > > > > Sheesh, you are correct. Sorry. > > Hmm, where do I find this information? It is recorded in last commit, > that changed the file, right? I'm not sure, if we can get this out of > the git tools?
I have no idea. Maybe not. If not, that's too bad.
I was just making a request of something that I think would be very helpful.
-- ~Randy
Junio C HamanoRe: gitweb: latest blob date (request)
Kay Sievers <kay.sievers@vrfy.org> writes:
> Hmm, where do I find this information? It is recorded in last commit, > that changed the file, right? I'm not sure, if we can get this out of > the git tools?
Yes we can. But it is rather expensive. You would do an equivalent of "git whatchanged" for each and every path.
Of course commit chain is immutable so you could do this once and cache the results.
Linus TorvaldsRe: latest blob date (request)
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