* [libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing
[not found] <bug-266-13@https.bugs.libre-soc.org/>
@ 2020-05-18 20:42 ` bugzilla-daemon
2020-05-18 20:53 ` Jacob Lifshay
2020-05-18 20:58 ` [libre-riscv-dev] [Bug 266] Allow read-only git clone over https bugzilla-daemon
` (2 subsequent siblings)
3 siblings, 1 reply; 9+ messages in thread
From: bugzilla-daemon @ 2020-05-18 20:42 UTC (permalink / raw)
To: libre-riscv-dev
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing
2020-05-18 20:42 ` [libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing bugzilla-daemon
@ 2020-05-18 20:53 ` Jacob Lifshay
2020-05-18 20:57 ` Luke Kenneth Casson Leighton
0 siblings, 1 reply; 9+ messages in thread
From: Jacob Lifshay @ 2020-05-18 20:53 UTC (permalink / raw)
To: Libre-RISCV General Development
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing
2020-05-18 20:53 ` Jacob Lifshay
@ 2020-05-18 20:57 ` Luke Kenneth Casson Leighton
0 siblings, 0 replies; 9+ messages in thread
From: Luke Kenneth Casson Leighton @ 2020-05-18 20:57 UTC (permalink / raw)
To: Libre-RISCV General Development
On Monday, May 18, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> 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.
awww okaaay :) can't i be totally lazy just once?
(thx for calling this one jacob)
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
* [libre-riscv-dev] [Bug 266] Allow read-only git clone over https
[not found] <bug-266-13@https.bugs.libre-soc.org/>
2020-05-18 20:42 ` [libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing bugzilla-daemon
@ 2020-05-18 20:58 ` bugzilla-daemon
2020-05-18 21:02 ` bugzilla-daemon
2020-05-18 21:07 ` bugzilla-daemon
3 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2020-05-18 20:58 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=266
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|deploy git commit-signing |Allow read-only git clone
|and tag-signing |over https
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 9+ messages in thread* [libre-riscv-dev] [Bug 266] Allow read-only git clone over https
[not found] <bug-266-13@https.bugs.libre-soc.org/>
2020-05-18 20:42 ` [libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing bugzilla-daemon
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
3 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2020-05-18 21:02 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=266
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.libre-soc.org/
| |show_bug.cgi?id=322
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 9+ messages in thread* [libre-riscv-dev] [Bug 266] Allow read-only git clone over https
[not found] <bug-266-13@https.bugs.libre-soc.org/>
` (2 preceding siblings ...)
2020-05-18 21:02 ` bugzilla-daemon
@ 2020-05-18 21:07 ` bugzilla-daemon
3 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2020-05-18 21:07 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=266
--- Comment #5 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #4)
> changing the topic of this bugreport.
Luke changed back to avoid confusion. Sincere thanks for taking the extra time!
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
* [libre-riscv-dev] [Bug 266] New: Allow read-only git clone over https
@ 2020-03-25 22:12 " bugzilla-daemon
2020-03-25 22:15 ` [libre-riscv-dev] [Bug 266] " bugzilla-daemon
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: bugzilla-daemon @ 2020-03-25 22:12 UTC (permalink / raw)
To: libre-riscv-dev
http://bugs.libre-riscv.org/show_bug.cgi?id=266
Bug ID: 266
Summary: Allow read-only git clone over https
Product: Libre-RISC-V Website
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: website
Assignee: lkcl@lkcl.net
Reporter: programmerjake@gmail.com
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
The git protocol is a insecure protocol, we should also support cloning over
https.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, back to index
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-266-13@https.bugs.libre-soc.org/>
2020-05-18 20:42 ` [libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing bugzilla-daemon
2020-05-18 20:53 ` Jacob Lifshay
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
2020-03-25 22:12 [libre-riscv-dev] [Bug 266] New: " bugzilla-daemon
2020-03-25 22:15 ` [libre-riscv-dev] [Bug 266] " bugzilla-daemon
2020-03-26 7:42 ` bugzilla-daemon
2020-03-26 10:09 ` bugzilla-daemon
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