From: Junio C Hamano <junkio@cox.net>
To: Sham Chukoury <eleusis@xmms.org>
Cc: git@vger.kernel.org, Kay Sievers <kay.sievers@suse.de>
Subject: Feeding some xmms2 gitweb enhancements back?
Date: Mon, 24 Apr 2006 02:01:15 -0700 [thread overview]
Message-ID: <7v1wvn8i04.fsf@assigned-by-dhcp.cox.net> (raw)
I was browsing
http://git.xmms.se/?p=gitweb-xmms2.git;a=shortlog
and noticed there are some nice enhancements and clean-ups that
the official gitweb distribution could probably use. I wonder
if it is a possibility for you to feed the following to Kay for
upstream inclusion after cleaning up?
* Navbar refactoring
* Move CSS out of gitweb.cgi
* Make CSS readable
I found these quite nice, from the pain last time I tried to
touch gitweb X-<. I suspect it wouldn't be a straight
cherry-pick, though...
* Add support for code highlighting in blob view
* Highlight more file types
Perhaps.
* Add category support via $GIT_DIR/category for project
* Show project tree git url on summary page
* Add committags support
Perhaps. This depends on the site organization and the
tracking system used.
* Snapshot links support
Running this on kernel.org might be a bit heavyweight and
sysadmins may not like it, but I like this.
reply other threads:[~2006-04-24 9:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7v1wvn8i04.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=eleusis@xmms.org \
--cc=git@vger.kernel.org \
--cc=kay.sievers@suse.de \
/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