From: Luben Tuikov <ltuikov@yahoo.com>
To: Junio C Hamano <junkio@cox.net>, Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, ltuikov@yahoo.com
Subject: Re: [PATCH] gitweb: tree view: hash_base and hash are now context sensitive
Date: Wed, 27 Sep 2006 15:53:42 -0700 (PDT) [thread overview]
Message-ID: <20060927225342.7695.qmail@web31801.mail.mud.yahoo.com> (raw)
In-Reply-To: <7v1wpxhkj9.fsf@assigned-by-dhcp.cox.net>
--- Junio C Hamano <junkio@cox.net> wrote:
> Luben Tuikov <ltuikov@yahoo.com> writes:
>
> > --- Jakub Narebski <jnareb@gmail.com> wrote:
> >> I think that this need some thinking over. For blob we have two
> >> "base" objects: tree which have specified blob, and commit which
> >> have tree which have specified blob. We might want to specify
> >> that all hash*base are to the commit-ish.
> >
> > Agreed, we should always refer to the commit-ish, for obvious
> > reasons.
> >
> > This patch doesn't make this decision though. It simply
> > sets hash_base to HEAD if not defined.
> >
> > Now, since "git-ls-tree" works on both commit-ish and
> > tree-ish, we are ok.
>
> I think so, too. Jakub?
Status? I see Jakub hasn't objected, and it is really important
for us to be able to link to "latest" binary blob -- for example
a PDF spec file.
Luben
next prev parent reply other threads:[~2006-09-27 22:53 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 [this message]
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
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=20060927225342.7695.qmail@web31801.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=junkio@cox.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).