unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: 51694-close@debbugs.gnu.org, botfiddler <botfiddler@runbox.com>
Subject: bug#51694: Closing without action
Date: Tue, 09 Nov 2021 21:54:24 +0100	[thread overview]
Message-ID: <87k0hhxcwr.fsf@nckx> (raw)
In-Reply-To: <E1mkDe6-0005nY-W2@rmmprod05.runbox>


[-- Attachment #1.1: Type: text/plain, Size: 834 bytes --]

Hi Michael,

OK, that's what I expected, but I had to ask.  Thanks!

May I publicly (hah) share your message to definitively close this
‘bug’ report?

Michael Albinus 写道:
> search engines will have indexed those bugs
> the bugs are spread via mailing lists

I might've been unclear: their request was not, AIUI, to make the 
data
disappear from ‘the Internet’ or its archives, so neither of the 
above
are relevant.  I agree that that would have been ludicrous, but it 
is
perfectly possible to edit your hosted copy…

…however, it's absolutely your prerogative to refuse as far as I'm
concerned[0], and I do sympathise with you not wanting to set this
kind of precedent.  Thanks for entertaining the question anyway! 
:-)

Kind regards,

T G-R

[0]: IANA(GDPR)L, and very glad of it.


[-- Attachment #1.2: Re: Removing personal info from existing bug --]
[-- Type: message/rfc822, Size: 4434 bytes --]

From: Michael Albinus <michael.albinus@gmx.de>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-debbugs@gnu.org
Subject: Re: Removing personal info from existing bug
Date: Tue, 09 Nov 2021 18:50:45 +0100
Message-ID: <87lf1xqkui.fsf@gmx.de>

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> Hi!

Hi Tobias,

> We received a request to edit an existing bug[0] to remove the
> submitters' full name, which was used by accident.  Is this possible?
>
>> Replace it
>> with Botfiddler or Sven if you need a real name. Sorry for the
>> bother
>> and thanks.
>
> Double thanks from me if it is :-)
>
> Now…  they then went ahead and signed *that* request with their full
> name.  Probably not understanding how the bug tracker works. If you
> would be willing to also edit their name out of [1], we'd approach
> triple levels of gratitude.

I'm sorry, but that won't work. The bug database is public, and so are
the date. Many search engines will have indexed those bugs already,
including the real names.

If you run a google search with "Fira Byvire Frirevav" (string puzzled
with rot13), the third hit will show the message on
<https://issues.guix.gnu.org/50371>.

Furthermore, the bugs are spread via mailing lists, for which we don't
have control. Full data are contained as well.

> I'll explain the nature of the bug tracker to them now.

Please do.

> Kind regards,
>
> T G-R

Best regards, Michael.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

      parent reply	other threads:[~2021-11-09 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 23:01 [bug#51694] issues.guix.org/50371 botfiddler
2021-11-09 16:26 ` [bug#51694] issues.guix.gnu.org/50371 Tobias Geerinckx-Rice via Guix-patches via
2021-11-09 20:54 ` Tobias Geerinckx-Rice via Guix-patches via [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k0hhxcwr.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=51694-close@debbugs.gnu.org \
    --cc=botfiddler@runbox.com \
    --cc=me@tobias.gr \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).