public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug admin/16584] New: Wiki edit attributions missing
Date: Fri, 14 Feb 2014 14:04:00 -0000 [thread overview]
Message-ID: <bug-16584-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16584
Bug ID: 16584
Summary: Wiki edit attributions missing
Product: glibc
Version: 2.19
Status: NEW
Severity: normal
Priority: P2
Component: admin
Assignee: unassigned at sourceware dot org
Reporter: jsm28 at gcc dot gnu.org
CC: carlos at redhat dot com, roland at gnu dot org
The recent removal of glibc wiki accounts for people without edit access broke
the attribution of various past non-spam edits. This attributtion should be
restored for all such edits to being the username by which the person chose to
be attributed (probably by restoring the accounts that made those edits and
protecting them from future purges).
https://sourceware.org/ml/libc-alpha/2014-02/msg00190.html has a list of such
edits for HomePage only.
https://web.archive.org/web/20111224071356/http://sourceware.org/glibc/wiki/HomePage?action=info
shows clearly that such edits did have attribution to a username, rather than
having been attributed only to a hostname all along.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-02-14 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 14:04 jsm28 at gcc dot gnu.org [this message]
2014-02-14 14:06 ` [Bug admin/16584] " jsm28 at gcc dot gnu.org
2014-02-14 19:48 ` jsm28 at gcc dot gnu.org
2014-02-14 20:35 ` carlos at redhat dot com
2014-06-13 8:15 ` fweimer at redhat dot com
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=bug-16584-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).