Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing
Date: Mon, 18 May 2020 13:53:43 -0700
Message-ID: <CAC2bXD5Z8eBTTMR7O5Nxy52JBHKvJMBH=MDeOCk_ixuiQWXzCg@mail.gmail.com> (raw)
In-Reply-To: <bug-266-13-MpxQXa01Sx@https.bugs.libre-soc.org/>

On Mon, May 18, 2020, 13:43 <bugzilla-daemon@libre-soc.org> wrote:

> https://bugs.libre-soc.org/show_bug.cgi?id=266
>
> Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Summary|Allow read-only git clone   |deploy git commit-signing
>                    |over https                  |and tag-signing
>
> --- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> changing the topic of this bugreport.


We really shouldn't just repurpose bug reports when the goal of the
original bug report is accomplished, since it makes it quite confusing to
people who weren't paying attention the whole time or are looking through
past bug reports. Additionally, nearly all the comments are on a totally
different topic than what the title was changed to.

Luke, please change the title back, close this bug, and create a new one.

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-266-13@https.bugs.libre-soc.org/>
2020-05-18 20:42 ` bugzilla-daemon
2020-05-18 20:53   ` Jacob Lifshay [this message]
2020-05-18 20:57     ` Luke Kenneth Casson Leighton
2020-05-18 20:58 ` [libre-riscv-dev] [Bug 266] Allow read-only git clone over https bugzilla-daemon
2020-05-18 21:02 ` bugzilla-daemon
2020-05-18 21:07 ` bugzilla-daemon

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='CAC2bXD5Z8eBTTMR7O5Nxy52JBHKvJMBH=MDeOCk_ixuiQWXzCg@mail.gmail.com' \
    --to=programmerjake@gmail.com \
    --cc=libre-riscv-dev@lists.libre-riscv.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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git