also sprach Anders Kaseorg ande...@mit.edu [2010.09.09.0121 +0200]:
I worry that this information is rather expensive to generate,
especially for a large repository like git.git or linux-2.6.git.
gitk tries to solve that problem by writing a cache into the
repository directory, but gitweb
On Thu, 9 Sep 2010, martin f krafft wrote:
I agree with you, but there's a fundamental difference: gitk (seems to)
generate this information up front for all commits, while gitweb only
needs to generate it for a single commit at a time. So the question is
really: are the required calls to
Package: gitweb
Version: 1:1.7.1-1.1
Severity: wishlist
Tags: upstream
It would be nice if gitweb's commit information (a=commit, and
possible a=commitdiff) included the same information gitk offers,
specicially which branches the commit is on, which tags it follows,
and which it precedes.
--
On Wed, 8 Sep 2010, martin f krafft wrote:
It would be nice if gitweb's commit information (a=commit, and possible
a=commitdiff) included the same information gitk offers, specicially
which branches the commit is on, which tags it follows, and which it
precedes.
I worry that this
4 matches
Mail list logo
