All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: tree view: hash_base and hash are now context sensitive
Date: Mon, 02 Oct 2006 00:27:36 +0200	[thread overview]
Message-ID: <efpfc3$765$1@sea.gmane.org> (raw)
In-Reply-To: 20060929233037.42926.qmail@web31808.mail.mud.yahoo.com

Luben Tuikov wrote:

> What this patch does is simply set "h" and/or "hb" to
> the string "HEAD" instead of the string "<SHA1 of HEAD>" when
> h/hb is not defined.

I guess there it is a good idea, but we should always think
over if we want "constant" link, always showing the same thing,
or a "variable" (or "news") link, showing current version.

Explicit sha1 hash as 'h'/'hb' gives persistent, cacheable link,
while e.g. "HEAD" gives "variable" link.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2006-10-01 22:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 19:47 [PATCH] gitweb: tree view: hash_base and hash are now context sensitive Luben Tuikov
2006-09-26 20:34 ` Jakub Narebski
2006-09-26 21:17   ` Luben Tuikov
2006-09-27  6:48     ` Junio C Hamano
2006-09-27 22:53       ` Luben Tuikov
2006-09-28 18:52         ` Luben Tuikov
2006-09-29  6:06           ` Junio C Hamano
2006-09-29 16:16             ` Luben Tuikov
2006-09-29 20:35               ` Jakub Narebski
2006-09-29 23:30                 ` Luben Tuikov
2006-10-01 22:27                   ` Jakub Narebski [this message]
2006-10-02 19:51                     ` Luben Tuikov
  -- strict thread matches above, loose matches on Subject: below --
2006-09-29 16:57 Luben Tuikov

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='efpfc3$765$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.