public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 4e6fcc73f14fbf16db9f84703bc6239a9f25bce7
Date: Sat, 19 Feb 2022 00:23:44 +0000	[thread overview]
Message-ID: <4K0q6m5KBpz2xhP@people01.haj.ipfire.org> (raw)

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

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  4e6fcc73f14fbf16db9f84703bc6239a9f25bce7 (commit)
      from  cf21dcaa979a9a27e946efb8af4ff66ffcf534f3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 4e6fcc73f14fbf16db9f84703bc6239a9f25bce7
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date:   Sat Feb 19 00:23:21 2022 +0000

    Fix Bugzilla URL in GCC LFS file
    
    Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 lfs/gcc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Difference in files:
diff --git a/lfs/gcc b/lfs/gcc
index 869c03380..f78891e24 100644
--- a/lfs/gcc
+++ b/lfs/gcc
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2021  IPFire Team  <info(a)ipfire.org>                     #
+# Copyright (C) 2007-2022  IPFire Team  <info(a)ipfire.org>                     #
 #                                                                             #
 # This program is free software: you can redistribute it and/or modify        #
 # it under the terms of the GNU General Public License as published by        #
@@ -180,7 +180,7 @@ endif
 
 EXTRA_CONFIG += \
 	--disable-multilib \
-	--with-bugurl=http://bugtracker.ipfire.org \
+	--with-bugurl=https://bugzilla.ipfire.org \
 	--disable-libunwind-exceptions \
 	--enable-gnu-unique-object
 


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2022-02-19  0:23 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=4K0q6m5KBpz2xhP@people01.haj.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@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