From: Jakub Narebski <jnareb@gmail•com>
To: git@vger•kernel.org
Subject: Re: [PATCH] gitweb: "raw" links to blobs at HEAD
Date: Tue, 26 Sep 2006 10:58:28 +0200 [thread overview]
Message-ID: <efaq3h$e65$2@sea.gmane.org> (raw)
In-Reply-To: 20060926053920.47709.qmail@web31802.mail.mud.yahoo.com
Luben Tuikov wrote:
> Currently there is no HTML interface which references (or
> can be externally referenced) to yield a _binary_ blob at
> HEAD. There is one for non-binary blobs, but none for
> binary ones.
You can in the same number of steps. First go to _tree_
at head, then click on "raw" link.
It's true that decision that binary files are automatically
redirected to "plain" ("raw") format, so they don't have "html"
output caused that there is no link for binary blob at head.
But I don't think that changing "raw" link to link to HEAD
version, while all other links are to current version is
a good idea...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-26 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 5:39 [PATCH] gitweb: "raw" links to blobs at HEAD Luben Tuikov
2006-09-26 6:46 ` Junio C Hamano
2006-09-26 18:53 ` Luben Tuikov
2006-09-26 8:58 ` Jakub Narebski [this message]
2006-09-26 20:20 ` 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='efaq3h$e65$2@sea.gmane.org' \
--to=jnareb@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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