git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: suggestions for gitweb

From
Petr Baudis <pasky@suse.cz>
Date
May 14, 2007, 09:58 UTC
Message-ID
<20070514095857.GI4489@pasky.or.cz>
In-Reply-To
<20070514085314.GY14859@MichaelsNB>
  Hi,
On Mon, May 14, 2007 at 10:53:15AM CEST, Michael Niedermayer wrote:
Show 14 quoted lines
> On Mon, May 14, 2007 at 04:36:09AM +0200, Petr Baudis wrote:
> > On Mon, May 14, 2007 at 04:00:02AM CEST, Michael Niedermayer wrote:
> > > i agree with you that she will click on 'history' and figure out what it is
> > > but if she wants to see the contents of one of the files then i think
> > > she will be confused and not know where to click,
> > 
> > I think she will just click on the filename - straightforward enough...?
> 
> yes and no :)
> i see 2 possible problems with this
> first if she starts from the summary page (which is from where she would
> start from if she clicked on 'ffmpeg') then she would see the recent 
> history but no directory/file names, she would have to click on 'tree' 
> here
  well, I guess our opinions on how hard it is to guess it through just
differ... :-)
Show 5 quoted lines
> also file size and last modified dates would be interresting on the tree
> page
> viewvc displays on its equivalent page, time since last change
> svn revission of the last change, the author/commiter of the last change
> and the corresponding abbreviated log entry
  I guess this is much easier to retrieve in svn than in git - you
actually have to walk all the history to figure out this information as
there's no global per-file info; so this is very troublesome
performance-wise. I think there were some patches on the mailinglist
that dit this, though I'm not sure. Might be reasonable to cache this
(and git history properties make it possible to nicely make a very
easily reusable cache for this information).
  About file sizes, that also has some extra performance hit, but in
this case I suspect that it would be totally negligible (if implemented
at the plumbing level) - and I admit that I would like to see file sizes
too, they can help orientation in a foreign source tree a lot.
-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Ever try. Ever fail. No matter. // Try again. Fail again. Fail better.
		-- Samuel Beckett
Previous: Michael NiedermayerNext: Jakub Narebski
Message 18 of 21 in “suggestions for gitweb”
  1. Michael NiedermayerMay 12, 2007
  2. Junio C HamanoMay 12, 2007
  3. Aaron GrayMay 12, 2007
  4. Jakub NarebskiMay 13, 2007
  5. Junio C HamanoMay 13, 2007
  6. Jakub NarebskiMay 13, 2007
  7. Lars HjemliMay 13, 2007
  8. Suggestions for cgit (was: Re: suggestions for gitweb)Jakub Narebski, May 14, 2007
  9. Lars HjemliMay 14, 2007
  10. Lars HjemliMay 15, 2007
  11. Michael NiedermayerMay 13, 2007
  12. Jakub NarebskiMay 13, 2007
  13. Junio C HamanoMay 14, 2007
  14. Petr BaudisMay 14, 2007
  15. Michael NiedermayerMay 14, 2007
  16. Petr BaudisMay 14, 2007
  17. Michael NiedermayerMay 14, 2007
  18. Petr BaudisMay 14, 2007
  19. Jakub NarebskiMay 14, 2007
  20. Michael NiedermayerMay 14, 2007
  21. Jan HudecMay 15, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.