git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jakub Narębski" <jnareb@gmail.com>
To: "Jürgen Kreileder" <jk@blackdown.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/4] gitweb: Don't append ';js=(0|1)' to external links
Date: Tue, 09 Apr 2013 19:59:05 +0200	[thread overview]
Message-ID: <516456E9.9070309@gmail.com> (raw)
In-Reply-To: <m2mwt7a8tz.fsf@zahir.fritz.box>

W dniu 09.04.2013 19:54, Jürgen Kreileder napisał:
> Jakub Narębski <jnareb@gmail.com> writes:
> 
>> Jürgen Kreileder wrote:
>>
>>> Don't add js parameters to links outside of gitweb itself.
>>
>> Hmmm... this limits adding ';js=(0|1)' to only links which begin with
>> $my_url, i.e. absolute links beginning with gitweb's base URL.
>>
>> Wouldn't that mean that most internal gitweb-generated links wouldn't
>> get ';js=(0|1)'?  href(..., -full => 1) is not the default...
> 
> No, link.href is always absolute in JavaScript - even if the emitted URL
> was relative.

Thanks, I didn't know that.

So, with that explanation:

Acked-by: Jakub Narebski <jnareb@gmail.com>

> Old: https://git.blackdown.de/old.cgi?p=contactalbum.git;a=summary;js=1
> New: https://git.blackdown.de/?p=contactalbum.git;a=summary;js=1
> 
> With the old version the external links in the description got ';js=1'
> appended.  With the new version, ';js=1' isn't on those links.
> Other links are the same in both versions.

Thanks.  This is a nice solution for a problem which I didn't know
how to solve (I was thinking about using <a class="internal" ...>,
but your solution is better).

-- 
Jakub Narębski

      reply	other threads:[~2013-04-09 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 20:09 [PATCH 3/4] gitweb: Don't append ';js=(0|1)' to external links Jürgen Kreileder
2013-04-09 15:16 ` Jakub Narębski
2013-04-09 17:54   ` Jürgen Kreileder
2013-04-09 17:59     ` Jakub Narębski [this message]

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=516456E9.9070309@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jk@blackdown.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;
as well as URLs for NNTP newsgroup(s).