From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EB8553858439; Tue, 26 Mar 2024 22:28:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EB8553858439 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1711492101; bh=eN8fD34o5E54cPK4b+0/vOSTDVLb6aA6cWBbSaRXoR8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Meu0g+x4mVOU284HJaJkbCmiPJ2sq98j4bTiZHiNTdVB28xDRC90ekvw5LkQVcPO5 F+Bl/kOG9DA8wdZSipBsyUuhCkvxYnXvzvj3k3YYYCNAVfUCJ2u62M2ZDeFTkiUBL/ IW+hhChznM/ezB8n8d81OlOB5g+bjrzzQLyh5gPA= From: "mark at klomp dot org" To: overseers@sourceware.org Subject: [Bug Bugzilla/31546] Bugzilla upgrade Date: Tue, 26 Mar 2024 22:28:20 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: sourceware X-Bugzilla-Component: Bugzilla X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: overseers at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31546 --- Comment #5 from Mark Wielaard --- (In reply to Fr=C3=A9d=C3=A9ric Buclin from comment #4) > (In reply to Mark Wielaard from comment #3) > > We can use this bug to make sure all patches/features we need/want are = in > > 6.0. > > Like the patches mentioned in this bug and things like the RH sitemap c= ode. >=20 > If there are specific features you want, and if they are not too invasive, > they could easily be implemented with the current version of Sourceware > Bugzilla. Please file separate bugs using Product:sourceware > Component:Bugzilla (not Infrastructure) and I can look at them. Thanks. I forgot there was a specific bugzilla component. I set the compone= nt of this bug, bug #29645 and bug #30610 to bugzilla now. Not sure those are = not too invasive and easy though. > One example > which comes to mind is inline history. See how I did it for Mageia Bugzil= la, > which is also running 5.0.4: >=20 > https://gitweb.mageia.org/web/bugs/commit/?id=3D8d9c748a5e694fb544c082128= c9756a0ca702334 Nice. And especially nice mageia is also using 5.0.4. So we can easily share patches. The patches I picked up from gentoo from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108473 were a bit of a pain because they are using 5.0.6. Like them we should also publish our bugzilla git repo. Is this inline history patch also upstream? And if so, in which version? 5.= 2 or 6.0? > (Note that I managed to loose my old SSH key when I bought my new PC, and= so > I can no longer access sourceware.org using ssh. Someone from overseers > would have to help me if you want me to help with Bugzilla.) I'll sent a private email to set that up. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=