* [libre-riscv-dev] [Bug 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-04-09 20:14 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=184
--- Comment #13 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #12)
> (In reply to Jacob Lifshay from comment #11)
>
> > I'm guessing the source address will be
> > git-mirroring@jacob-build-server.programmerjake.tk
>
> ah if you install ssmtp and set it up similar to how it is done on the
> ppc64 server, we can make it look like the messages are coming from
> libre-soc.org.
If we use the lettre.at library for sending build emails, we could set it to
just connect directly to libre-soc.org over the vpn without needing a local
email server. We could also make the source address be builds@libre-soc.org
instead of git-mirroring@jacob-build-server.programmerjake.tk that way it won't
change if we move to a different server.
> take a look in the /etc/ssmtp directory on the pp64 server
>
> > If you can, the Reply-To: header for both special-use mailing lists should
> > be set to libre-soc-dev@libre-soc.org
>
> hmmm a case could be made for teaching people "um no you go to the
> bugtracker" by rejecting replies. otherwise they will think that they
> _should_ reply and we are back to square one.
We could add a link to the new bug page to the emails sent out to the builds
mailing list. If we are going to reject replies we should set Reply-To: to
no-reply@libre-soc.org instead of leaving it as the default.
--
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
* Re: [libre-riscv-dev] gitlab-ci-archiver status
From: Luke Kenneth Casson Leighton @ 2020-04-09 20:24 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6Ui4j9PiWkc1ofn_xek+HmsM0qr8VvrRah885Dp3gKPA@mail.gmail.com>
On Thu, Apr 9, 2020 at 9:03 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> > ahh, fantastic.
> >
> > is that in a position to hand over to frieder or alain?
> >
>
> Currently it needs modification to respond properly to adding a new build
> to an existing pipeline (if someone clicks rebuild), it currently ignores
> all pipelines already committed to the archive git repo. I'd estimate maybe
> an hour of work by an experienced Rust programmer is needed.
ok time's been committed, might as well finish it.
> It also needs code to send out the build failure emails, or that could be
> done by a shell script by parsing all the new commits -- so an hour of work
> in either bash or Rust
the general UNIX philosohpy is that one program do one task and do it
well. therefore farm that task to an external program.
l.
_______________________________________________
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
* Re: [libre-riscv-dev] GitLab CI Archiver
From: Jacob Lifshay @ 2020-04-09 20:25 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDx=pYNXvapRZyxySeL2VeC_cGQC44X=ye0W-kUcqJMzgg@mail.gmail.com>
On Wed, Apr 8, 2020, 09:16 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Wed, Apr 8, 2020 at 4:42 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > Sorry, I ended up writing a Rust program that does at least part of
> > what we need (I thought it might take an hour or two -- it took 10):
>
> we need to be careful about that: sysadmin tasks are typically done in
> bash, using awk, sed, grep, curl and others.
>
> alain will definitely be unable to work on rust programs: he'll be
> able to install and use them but it will take him potentially 3-8
> months full-time (doing nothing else) to get to the point where he
> could _modify_ - take over - anything written in rust, and maintain
> it.
>
Once the modifications mentioned in the other thread are done, it's highly
likely to not need modification. I split out nearly all the things that are
likely to change into an external toml config file, which should be easy to
modify/understand. It also has full-featured command line help and
autocompletion thanks to the structopt and clap libraries.
I'm not the only one who knows Rust if something goes wrong, and most of
the code is quite simple (though it could just be me that thinks that since
I've been working on Kazan which is *very* complex).
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
* [libre-riscv-dev] [Bug 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-04-09 20:28 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=184
--- Comment #14 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #13)
> (In reply to Luke Kenneth Casson Leighton from comment #12)
> > (In reply to Jacob Lifshay from comment #11)
> >
> > > I'm guessing the source address will be
> > > git-mirroring@jacob-build-server.programmerjake.tk
> >
> > ah if you install ssmtp and set it up similar to how it is done on the
> > ppc64 server, we can make it look like the messages are coming from
> > libre-soc.org.
>
> If we use the lettre.at library for sending build emails, we could set it to
> just connect directly to libre-soc.org over the vpn without needing a local
> email server.
ssmtp is not a local email server it's a redirector.
the less that gets done here the better.
can you arrange for the command to call an external command - the faster
this gets done in the least amount of time the better.
(there's no need to use a complicated advanced rust mail library:
get the information out as fast as possible and let *another*
external command do that job, this provides flexibility)
> We could also make the source address be builds@libre-soc.org
> instead of git-mirroring@jacob-build-server.programmerjake.tk that way it
> won't change if we move to a different server.
yes.
> > take a look in the /etc/ssmtp directory on the pp64 server
> >
> > > If you can, the Reply-To: header for both special-use mailing lists should
> > > be set to libre-soc-dev@libre-soc.org
> >
> > hmmm a case could be made for teaching people "um no you go to the
> > bugtracker" by rejecting replies. otherwise they will think that they
> > _should_ reply and we are back to square one.
>
> We could add a link to the new bug page to the emails sent out to the builds
> mailing list. If we are going to reject replies we should set Reply-To: to
> no-reply@libre-soc.org instead of leaving it as the default.
yep good idea.
--
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
* Re: [libre-riscv-dev] gitlab-ci-archiver status
From: Jacob Lifshay @ 2020-04-09 20:31 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwnXBeRzMMJmcuZAsR1hOec=Xx6kvmsuYasO_sDYr82Gw@mail.gmail.com>
On Thu, Apr 9, 2020, 13:25 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Thu, Apr 9, 2020 at 9:03 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> > It also needs code to send out the build failure emails, or that could be
> > done by a shell script by parsing all the new commits -- so an hour of
> work
> > in either bash or Rust
>
> the general UNIX philosohpy is that one program do one task and do it
> well. therefore farm that task to an external program.
>
Ok, though both of calling out to sendmail with all the correct parameters
or writing an external script to parse the commits and then call sendmail
are likely to require much more code than just calling a library like
lettre.at even with the additional code for reading the config options from
the config file.
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
* Re: [libre-riscv-dev] gitlab-ci-archiver status
From: Luke Kenneth Casson Leighton @ 2020-04-09 21:48 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6cgfvQFPkjS6vabYUJERd2ZPV+9oyP3+O8A2ApmK2XPg@mail.gmail.com>
On Thu, Apr 9, 2020 at 9:31 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> Ok, though both of calling out to sendmail with all the correct parameters
> or writing an external script to parse the commits and then call sendmail
> are likely to require much more code than just calling a library like
> lettre.at even with the additional code for reading the config options from
> the config file.
hm, shouldn't be: it's just exec(), right? exec() with a list of
arguments, one of which is the tmp file that the message is saved in?
anyway if it's really that much more complicated just do it - but
please keep it expedient and rely on the existence of intermediary
servers (like the SMTP service on the VPN at 10.6.0.1, port 25)
l.
_______________________________________________
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
* Re: [libre-riscv-dev] gitlab-ci-archiver status
From: Jacob Lifshay @ 2020-04-09 21:54 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyG-J0ZEdHtzpJ1AZyO_658VOF9aDHWzQQ-bpuBpJ3LJw@mail.gmail.com>
On Thu, Apr 9, 2020, 14:48 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> anyway if it's really that much more complicated just do it - but
>
please keep it expedient and rely on the existence of intermediary
> servers (like the SMTP service on the VPN at 10.6.0.1, port 25)
>
lettre.at is specifically designed to connect to a relay server, so that
won't be an issue.
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
* [libre-riscv-dev] POWER virtual coffee 5 mins (now)
From: lkcl . @ 2020-04-09 21:56 UTC (permalink / raw)
To: Libre-RISCV General Development,
Roberto Innocenti - Gnu/Linux PowerPC notebook
https://openpowerfoundation.org/openpower-virtual-coffee-calls/
_______________________________________________
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
* Re: [libre-riscv-dev] gitlab-ci-archiver status
From: Luke Kenneth Casson Leighton @ 2020-04-09 23:19 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4j-aJz854cap_WyKqx85syQJp3PYVQ4ftm4VR1q7vBrg@mail.gmail.com>
ah i just realised, you may be tempted to assume that the outgoing command
is not 100% reliable and thus start writing retry and store and forward
code.
this is why i said assume the UNIX philosophy do one task and do it well.
other services do store and forward so use them.
we can always install exim4 as a relay.
so on consideration please use whatever wrapper rust puts around popen2 or
popen3, shove the log out on stdout, no command options (no env vars) where
the command is from the config file, no paramers, nothing.
it then becomes a 5 minute job to write a bash script "mail -s "build log"
fred@foo"
if the command does produce stderr output shove that into the error logs
and forget about it.
we need to get this handed over to alain and frieder as soon as possible.
this or equivalent will do
https://doc.rust-lang.org/1.8.0/libc/fn.popen.html
l.
--
---
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
* Re: [libre-riscv-dev] gitlab-ci-archiver status
From: Luke Kenneth Casson Leighton @ 2020-04-10 1:56 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzo+F9-OYcthagzDPOE2LbrHLUZOYbHMaCGFT8Atu666w@mail.gmail.com>
https://docs.rs/subprocess/0.1.18/subprocess/struct.Popen.html
this one's better. example which is pretty much exactly what is needed
should be 5 minutes work to add and test.
https://docs.rs/subprocess/0.2.4/subprocess/
args if needed which they really shouldn't go in the array as first arg to
Popen.
anything complicated pass it to stdout in simple one line newline one line
newline form.
l.
--
---
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
* Re: [libre-riscv-dev] gitlab-ci-archiver status
From: Jacob Lifshay @ 2020-04-10 2:27 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxoYotjTNSAB=uF5=XwqvyAPuy82c7VDD55F1oA5fUfXw@mail.gmail.com>
On Thu, Apr 9, 2020, 18:57 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> https://docs.rs/subprocess/0.1.18/subprocess/struct.Popen.html
>
> this one's better. example which is pretty much exactly what is needed
> should be 5 minutes work to add and test.
>
I was planning on using the program invocation functionality in the Rust
standard library:
https://doc.rust-lang.org/std/process/struct.Command.html
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
* Re: [libre-riscv-dev] gitlab-ci-archiver status
From: Luke Kenneth Casson Leighton @ 2020-04-10 12:08 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4TsYCSX3GJkx=e_UnrOLsdy1xeUKzuHr+a5a2C21CYkw@mail.gmail.com>
On Friday, April 10, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Thu, Apr 9, 2020, 18:57 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
> > https://docs.rs/subprocess/0.1.18/subprocess/struct.Popen.html
> >
> > this one's better. example which is pretty much exactly what is needed
> > should be 5 minutes work to add and test.
> >
>
> I was planning on using the program invocation functionality in the Rust
> standard library:
> https://doc.rust-lang.org/std/process/struct.Command.html
yeah that looks overkill (expect capability builtin) however the interface
looks pretty clean and the output() function has both stdout and stderr
capturable.
also the command return result (exit code) is available, which is important
to use the convention "0" as success and all nonzero values to be err
logged.
one thing is not obvious, if it is sync or async.
l.
--
---
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
* [libre-riscv-dev] [Bug 158] NLNet 2019 Formal Correctness Proofs toplevel 2019-10-032
From: bugzilla-daemon @ 2020-04-10 14:16 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-158-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=158
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |IN_PROGRESS
--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
signed, received from Bob Goudriaan.
--
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
* Re: [libre-riscv-dev] morphing 6600 code to use power decoder
From: Luke Kenneth Casson Leighton @ 2020-04-10 15:01 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzz4=cd90=e21oYZn1OphRpcFsoWhLf0aMoTtJnjOcFMA@mail.gmail.com>
okaay, i have a first successful - one instruction (an add) -
execution of an "internal op" which is manually placed into the
instruction queue. adding the POWER decoder in front of that should
be a trivial exercise.
the code's been... messed about somewhat, to get it functional, and
the LDST and Branch Comp Units also need converting. however the core
out-of-order engine remains exactly the same, so this again should
just be a straightforward exercise.
we do need to write a "proper" Integer ALU - one that uses
PartitionedSignal for operations. this will be where all the pieces
and hard work that everyone's put in will gel together.
l.
_______________________________________________
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
* [libre-riscv-dev] [Bug 276] SR NAND Latch needed in nmigen
From: bugzilla-daemon @ 2020-04-10 15:04 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-276-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=276
--- Comment #15 from whitequark@whitequark.org ---
Cxxrtl is upstream in Yosys, including SR latch support.
--
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
* [libre-riscv-dev] [Bug 276] SR NAND Latch needed in nmigen
From: bugzilla-daemon @ 2020-04-10 16:16 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-276-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=276
--- Comment #16 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to whitequark from comment #15)
> Cxxrtl is upstream in Yosys, including SR latch support.
fantastic, that's really appreciated. we have *sigh* a bureaucratic
MoU to be signed (4 - now 5 - people waiting on EUR for that one).
not least because of all the other support that you've given,
and recognising that this is really strategically crucial for us, if
you have time to write a short demo / unit test of the srlatch
i think we can easily justify increasing this one to EUR 300?
(although i'm sure it would be fairly trivial for you to write,
that's because you're most familiar with the code).
--
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
* Re: [libre-riscv-dev] gitlab-ci-archiver status
From: Jacob Lifshay @ 2020-04-10 17:15 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwUfNu_WSntQMsRR_3ExZ9e6BHv+TZi2Yi2cnkdZn_tQA@mail.gmail.com>
On Fri, Apr 10, 2020, 05:09 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Friday, April 10, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> > I was planning on using the program invocation functionality in the Rust
> > standard library:
> > https://doc.rust-lang.org/std/process/struct.Command.html
>
>
> yeah that looks overkill (expect capability builtin) however the interface
> looks pretty clean and the output() function has both stdout and stderr
> capturable.
>
The idea is to expose all the commonly used functionality in a
cross-platform manner, there are extension traits that add additional
functionality for Unix or Windows.
Unix extension trait:
https://doc.rust-lang.org/std/os/unix/process/trait.CommandExt.html
>
> also the command return result (exit code) is available, which is important
> to use the convention "0" as success and all nonzero values to be err
> logged.
>
> one thing is not obvious, if it is sync or async.
>
Depends on which functions you use if they are blocking, though it is not
async in the sense of Futures.
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
* [libre-riscv-dev] [Bug 276] SR NAND Latch needed in nmigen
From: bugzilla-daemon @ 2020-04-10 17:27 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-276-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=276
Jacob Lifshay <programmerjake@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |programmerjake@gmail.com
--- Comment #18 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to whitequark from comment #17)
> Created attachment 50 [details]
> SR latch demonstration
For some reason, bugzilla doesn't send out notifications for creating
attachments.
Thanks, whitequark, looks good to me!
--
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
* [libre-riscv-dev] [Bugzilla] Your account libre-riscv-dev@lists.libre-riscv.org is being impersonated
From: bugzilla-daemon @ 2020-04-10 17:38 UTC (permalink / raw)
To: libre-riscv-dev
Jacob Lifshay <programmerjake@gmail.com> has used the 'sudo' feature to access
Bugzilla using your account.
Jacob Lifshay <programmerjake@gmail.com> provided the following reason for doing this:
try to update email preferences to get notifications for adding attachments
If you feel that this action was inappropriate, please contact
lkcl@lkcl.net. For more information on this feature,
visit <https://bugs.libre-soc.org/page.cgi?id=sudo.html>.
_______________________________________________
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
* Re: [libre-riscv-dev] [Bugzilla] Your account libre-riscv-dev@lists.libre-riscv.org is being impersonated
From: Jacob Lifshay @ 2020-04-10 17:49 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <E1jMxc8-0005mC-OH@libre-soc.org>
On Fri, Apr 10, 2020, 10:39 <bugzilla-daemon@libre-soc.org> wrote:
> Jacob Lifshay <programmerjake@gmail.com> has used the 'sudo' feature
> to access
> Bugzilla using your account.
>
> Jacob Lifshay <programmerjake@gmail.com> provided the following
> reason for doing this:
> try to update email preferences to get notifications for adding attachments
Unfortunately, it didn't seem to work, since I added
https://bugs.libre-soc.org/show_bug.cgi?id=85#c1
and it didn't notify anyone.
Luke, we should try to fix this.
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
* Re: [libre-riscv-dev] [Bugzilla] Your account libre-riscv-dev@lists.libre-riscv.org is being impersonated
From: Luke Kenneth Casson Leighton @ 2020-04-10 17:49 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <E1jMxc8-0005mC-MX@libre-soc.org>
On Fri, Apr 10, 2020 at 6:38 PM <bugzilla-daemon@libre-soc.org> wrote:
>
> Jacob Lifshay <programmerjake@gmail.com> has used the 'sudo' feature to access
> Bugzilla using your account.
lucky bugzilla-daemon :)
_______________________________________________
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
* Re: [libre-riscv-dev] [Bugzilla] Your account libre-riscv-dev@lists.libre-riscv.org is being impersonated
From: Luke Kenneth Casson Leighton @ 2020-04-10 17:56 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4wyLis4fdjKCebPXKBoLwtYe9Q-R3z5MM05ewsLSXGEg@mail.gmail.com>
On Fri, Apr 10, 2020 at 6:49 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Fri, Apr 10, 2020, 10:39 <bugzilla-daemon@libre-soc.org> wrote:
>
> > Jacob Lifshay <programmerjake@gmail.com> has used the 'sudo' feature
> > to access
> > Bugzilla using your account.
> >
> > Jacob Lifshay <programmerjake@gmail.com> provided the following
> > reason for doing this:
> > try to update email preferences to get notifications for adding attachments
>
>
>
> Unfortunately, it didn't seem to work, since I added
> https://bugs.libre-soc.org/show_bug.cgi?id=85#c1
> and it didn't notify anyone.
>
> Luke, we should try to fix this.
somewhere, somewhere, there's some settings i switched off, so that
the amount of bugzilla-spam is reduced. i just can't remember now,
where. did some preliminary searching, going through a ton of
options, couldn't find it immediately.
l.
l.
_______________________________________________
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
* Re: [libre-riscv-dev] [Bugzilla] Your account libre-riscv-dev@lists.libre-riscv.org is being impersonated
From: Jacob Lifshay @ 2020-04-10 18:10 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyy6RcfihEvWci7ZrefEn=vA538SsRBCdE8pLeLOEfs1w@mail.gmail.com>
On Fri, Apr 10, 2020, 10:56 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Fri, Apr 10, 2020 at 6:49 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > On Fri, Apr 10, 2020, 10:39 <bugzilla-daemon@libre-soc.org> wrote:
> > > Jacob Lifshay <programmerjake@gmail.com> provided the following
> > > reason for doing this:
> > > try to update email preferences to get notifications for adding
> attachments
> >
> > Unfortunately, it didn't seem to work, since I added
> > https://bugs.libre-soc.org/show_bug.cgi?id=85#c1
> > and it didn't notify anyone.
> >
> > Luke, we should try to fix this.
>
> somewhere, somewhere, there's some settings i switched off, so that
> the amount of bugzilla-spam is reduced. i just can't remember now,
> where. did some preliminary searching, going through a ton of
> options, couldn't find it immediately.
>
I turned on attachment emails at
https://bugs.libre-soc.org/userprefs.cgi?tab=email for the mailing list,
didn't seem to help.
I also turned it on for other changes since it seemed like a good idea to
get notified when anyone changes how much money is assigned to a bug, since
anyone can sign up and start changing things.
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
* Re: [libre-riscv-dev] [Bugzilla] Your account libre-riscv-dev@lists.libre-riscv.org is being impersonated
From: Luke Kenneth Casson Leighton @ 2020-04-10 18:18 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD70+iRqSrNtNyNC4n+h99XmX+c8zsKUCk4raisoPAaYFw@mail.gmail.com>
On Fri, Apr 10, 2020 at 7:11 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Fri, Apr 10, 2020, 10:56 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
> > On Fri, Apr 10, 2020 at 6:49 PM Jacob Lifshay <programmerjake@gmail.com>
> > wrote:
> >
> > > On Fri, Apr 10, 2020, 10:39 <bugzilla-daemon@libre-soc.org> wrote:
> > > > Jacob Lifshay <programmerjake@gmail.com> provided the following
> > > > reason for doing this:
> > > > try to update email preferences to get notifications for adding
> > attachments
> > >
> > > Unfortunately, it didn't seem to work, since I added
> > > https://bugs.libre-soc.org/show_bug.cgi?id=85#c1
> > > and it didn't notify anyone.
> > >
> > > Luke, we should try to fix this.
> >
> > somewhere, somewhere, there's some settings i switched off, so that
> > the amount of bugzilla-spam is reduced. i just can't remember now,
> > where. did some preliminary searching, going through a ton of
> > options, couldn't find it immediately.
> >
>
> I turned on attachment emails at
> https://bugs.libre-soc.org/userprefs.cgi?tab=email for the mailing list,
> didn't seem to help.
this might just be personal user preferences.
l.
_______________________________________________
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
* [libre-riscv-dev] [Bug 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-04-10 18:27 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=184
--- Comment #15 from Jacob Lifshay <programmerjake@gmail.com> ---
Maybe it would be a good idea to ask marc.info to add our mailing lists to
their archive:
https://marc.info/?q=about
--
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
page: next prev latest
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