From: Robert Luberda <robert@debian.org>
To: git@vger.kernel.org
Subject: Two gitweb bugs related to javascript-actions
Date: Tue, 22 Jul 2014 22:41:43 +0200 [thread overview]
Message-ID: <53CECC87.7030209@debian.org> (raw)
Hi
Some time ago I reported the two following bugs to Debian BTS,
could you please look at them?
1. http://bugs.debian.org/741883 -- gitweb blame does not work
correctly when $feature{'javascript-actions'} is enabled
This should be one-line change fix, which I really would like to be
applied to the git package itself, not to do the same change over and
over again every time my gitweb package is updated on my system.
2. https://bugs.debian.org/741884 feature{'javascript-actions'} breaks
external links
This might be more challenging, but the simplest approach would be avoid
adding those strange '[#?]js=1' parts to non-gitweb-generated links.
Thanks a lot,
robert
next reply other threads:[~2014-07-22 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 20:41 Robert Luberda [this message]
2018-12-16 23:24 ` [PATCH] gitweb: correctly store previous rev in javascript-actions mode Jonathan Nieder
2019-10-27 9:14 ` Robert Luberda
2019-10-27 10:27 ` Jakub Narebski
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=53CECC87.7030209@debian.org \
--to=robert@debian.org \
--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 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).