public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Redirect to bugzilla page for invalid bug number on new wiki
Date: Tue, 20 Aug 2019 21:01:20 +0100	[thread overview]
Message-ID: <327376CB-4310-4283-900A-09D2E5A829D1@ipfire.org> (raw)
In-Reply-To: <11442719-C4C9-4F29-AC56-901670954D56@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

Hi,

Yes, this is a function to make references to bugs easier.

I changed it that it will only match numbers greater than 10000 which is our minimum bug number.

Thanks for reporting this. You can file things like this into BZ, please.

Best,
-Michael

> On 19 Aug 2019, at 21:55, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
> 
> There seems to be a quick link to bugzilla.  When I click on a wiki “#1", I end up on a bugzilla page for an invalid bug number.
> 
> Here is where I see the redirect:
> https://wiki.ipfire.org/addons/tor/why-use-tor
> 
> Just click on the #1 or the #2.
> 
> Is this a markdown enhancement? Or?  This doesn’t seem like a bug, but I can add it to bugzilla if needed.
> 
> I can change the tor webpage from:
> 
> ## #1 - Tor does not encrypt your content
> -to-
> ## 1) Tor does not encrypt your content
> 
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> https://lists.ipfire.org/mailman/listinfo/documentation


      reply	other threads:[~2019-08-20 20:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 20:55 Jon Murphy
2019-08-20 20:01 ` Michael Tremer [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=327376CB-4310-4283-900A-09D2E5A829D1@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=documentation@lists.ipfire.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