* [libre-riscv-dev] crowdsupply updates
@ 2020-04-01 16:02 Luke Kenneth Casson Leighton
2020-04-01 16:08 ` [libre-riscv-dev] IMPORTANT - PLEASE REMOVE AND RE-CHECKOUT CROWDSUPPLY REPOSITORY " Luke Kenneth Casson Leighton
2020-04-01 16:14 ` [libre-riscv-dev] " Luke Kenneth Casson Leighton
0 siblings, 2 replies; 8+ messages in thread
From: Luke Kenneth Casson Leighton @ 2020-04-01 16:02 UTC (permalink / raw)
To: Libre-RISCV General Development
https://libre-riscv.org/index/Updates/March_2020/
yehowshua i removed the update because it wasn't discussed. the
consequences of pre-publishing an update via our own website are very
simple: Crowdsupply will not publish it at all.
therefore, publishing it via our website will be detrimental to the project.
also i specifically mentioned that Crowdsupply has over 600
subscribers that the updates go out to.
i now have to spend time working out how to revert gitolite3
repositories in order to remove the update, which will involve a force
push-master.
when i have done so please can everyone destroy their working copy of
the crowdsupply repository, re-checking-out a new one.
thanks.
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 [flat|nested] 8+ messages in thread
* [libre-riscv-dev] IMPORTANT - PLEASE REMOVE AND RE-CHECKOUT CROWDSUPPLY REPOSITORY Re: crowdsupply updates
2020-04-01 16:02 [libre-riscv-dev] crowdsupply updates Luke Kenneth Casson Leighton
@ 2020-04-01 16:08 ` " Luke Kenneth Casson Leighton
2020-04-01 17:50 ` Jacob Lifshay
2020-04-01 16:14 ` [libre-riscv-dev] " Luke Kenneth Casson Leighton
1 sibling, 1 reply; 8+ messages in thread
From: Luke Kenneth Casson Leighton @ 2020-04-01 16:08 UTC (permalink / raw)
To: Libre-RISCV General Development
On Wed, Apr 1, 2020 at 5:02 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> when i have done so please can everyone destroy their working copy of
> the crowdsupply repository, re-checking-out a new one.
ok that's done: i had to edit the bare repository master file,
refs/head/master, to get it to "listen". this could have resulted in
corruption of the wiki.
if you have write access, please ensure that you check out a NEW copy
of the crowdsupply git repository, otherwise if you did a "git pull"
recently it will be the *wrong master* and will cause massive
problems.
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 [flat|nested] 8+ messages in thread
* Re: [libre-riscv-dev] crowdsupply updates
2020-04-01 16:02 [libre-riscv-dev] crowdsupply updates Luke Kenneth Casson Leighton
2020-04-01 16:08 ` [libre-riscv-dev] IMPORTANT - PLEASE REMOVE AND RE-CHECKOUT CROWDSUPPLY REPOSITORY " Luke Kenneth Casson Leighton
@ 2020-04-01 16:14 ` " Luke Kenneth Casson Leighton
2020-04-01 16:18 ` Immanuel, Yehowshua U
1 sibling, 1 reply; 8+ messages in thread
From: Luke Kenneth Casson Leighton @ 2020-04-01 16:14 UTC (permalink / raw)
To: Libre-RISCV General Development
On Wed, Apr 1, 2020 at 5:02 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> https://libre-riscv.org/index/Updates/March_2020/
>
> yehowshua i removed the update because it wasn't discussed.
please, please, don't put the contents of crowdsupply updates onto the
website. yes create *links* to the updates (and a copy of the
summary) *when they are published*, and also, for drafts, put a
warning, " preliminary: this is a draft, being edited, NOT PUBLISHED"
message (and link to the source) but please, really, *do not* put the
actual contents on the wiki.
firstly, they're duplicates. which one gets edited? which is the
canonical version?
secondly, it makes crowdsupply look "unimportant"
thirdly, joshua has - a number of times - seen updates that i've
written elsewhere, and silently *not published what i wrote* on
crowdsupply, as a result. this is perfectly reasonable of him to
decide to do.
fourthly, the website does *not* have an associated "updates mailing
list". there's something like 600 subscribers to the crowdsupply
pre-launch campaign, and if the page goes onto the wiki, we *do not
get a notification sent out to all those people*.
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 [flat|nested] 8+ messages in thread
* Re: [libre-riscv-dev] crowdsupply updates
2020-04-01 16:14 ` [libre-riscv-dev] " Luke Kenneth Casson Leighton
@ 2020-04-01 16:18 ` Immanuel, Yehowshua U
2020-04-01 16:33 ` Immanuel, Yehowshua U
0 siblings, 1 reply; 8+ messages in thread
From: Immanuel, Yehowshua U @ 2020-04-01 16:18 UTC (permalink / raw)
To: Libre-RISCV General Development
I had meant to remove it yesterday.
My apologies,
Yehowshua
_______________________________________________
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] 8+ messages in thread
* Re: [libre-riscv-dev] crowdsupply updates
2020-04-01 16:18 ` Immanuel, Yehowshua U
@ 2020-04-01 16:33 ` Immanuel, Yehowshua U
2020-04-01 17:39 ` Luke Kenneth Casson Leighton
0 siblings, 1 reply; 8+ messages in thread
From: Immanuel, Yehowshua U @ 2020-04-01 16:33 UTC (permalink / raw)
To: Libre-RISCV General Development
On this note however, do you think its a good idea to put a link to crowd supply?
Yehowshua
_______________________________________________
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] 8+ messages in thread
* Re: [libre-riscv-dev] crowdsupply updates
2020-04-01 16:33 ` Immanuel, Yehowshua U
@ 2020-04-01 17:39 ` Luke Kenneth Casson Leighton
0 siblings, 0 replies; 8+ messages in thread
From: Luke Kenneth Casson Leighton @ 2020-04-01 17:39 UTC (permalink / raw)
To: Libre-RISCV General Development
On Wed, Apr 1, 2020 at 5:33 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> On this note however, do you think its a good idea to put a link to crowd supply?
yehyeh, i like the idea of the summaries and links to CS.
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 [flat|nested] 8+ messages in thread
* Re: [libre-riscv-dev] IMPORTANT - PLEASE REMOVE AND RE-CHECKOUT CROWDSUPPLY REPOSITORY Re: crowdsupply updates
2020-04-01 16:08 ` [libre-riscv-dev] IMPORTANT - PLEASE REMOVE AND RE-CHECKOUT CROWDSUPPLY REPOSITORY " Luke Kenneth Casson Leighton
@ 2020-04-01 17:50 ` Jacob Lifshay
2020-04-01 17:59 ` Luke Kenneth Casson Leighton
0 siblings, 1 reply; 8+ messages in thread
From: Jacob Lifshay @ 2020-04-01 17:50 UTC (permalink / raw)
To: Libre-RISCV General Development
On Wed, Apr 1, 2020, 09:09 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Wed, Apr 1, 2020 at 5:02 PM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
>
> > when i have done so please can everyone destroy their working copy of
> > the crowdsupply repository, re-checking-out a new one.
>
> ok that's done: i had to edit the bare repository master file,
> refs/head/master, to get it to "listen". this could have resulted in
> corruption of the wiki.
>
> if you have write access, please ensure that you check out a NEW copy
> of the crowdsupply git repository, otherwise if you did a "git pull"
> recently it will be the *wrong master* and will cause massive
> problems.
>
Apparently, my master is at the same commit as the master on
https://git.libre-riscv.org/?p=crowdsupply.git;a=summary so I won't need to
re-clone.
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] 8+ messages in thread
* Re: [libre-riscv-dev] IMPORTANT - PLEASE REMOVE AND RE-CHECKOUT CROWDSUPPLY REPOSITORY Re: crowdsupply updates
2020-04-01 17:50 ` Jacob Lifshay
@ 2020-04-01 17:59 ` Luke Kenneth Casson Leighton
0 siblings, 0 replies; 8+ messages in thread
From: Luke Kenneth Casson Leighton @ 2020-04-01 17:59 UTC (permalink / raw)
To: Libre-RISCV General Development
On Wed, Apr 1, 2020 at 6:50 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> Apparently, my master is at the same commit as the master on
> https://git.libre-riscv.org/?p=crowdsupply.git;a=summary so I won't need to
> re-clone.
yes if you didn't git pull today it's fine.
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 [flat|nested] 8+ messages in thread
end of thread, back to index
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-01 16:02 [libre-riscv-dev] crowdsupply updates Luke Kenneth Casson Leighton
2020-04-01 16:08 ` [libre-riscv-dev] IMPORTANT - PLEASE REMOVE AND RE-CHECKOUT CROWDSUPPLY REPOSITORY " Luke Kenneth Casson Leighton
2020-04-01 17:50 ` Jacob Lifshay
2020-04-01 17:59 ` Luke Kenneth Casson Leighton
2020-04-01 16:14 ` [libre-riscv-dev] " Luke Kenneth Casson Leighton
2020-04-01 16:18 ` Immanuel, Yehowshua U
2020-04-01 16:33 ` Immanuel, Yehowshua U
2020-04-01 17:39 ` Luke Kenneth Casson Leighton
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