Bug 628 - restore mistaken removal of OpenPOWER from wiki
Summary: restore mistaken removal of OpenPOWER from wiki
Status: CONFIRMED
Alias: None
Product: Libre-SOC Website
Classification: Unclassified
Component: website (show other bugs)
Version: unspecified
Hardware: PC Linux
: High enhancement
Assignee: Alain D D Williams
URL:
Depends on:
Blocks:
 
Reported: 2021-04-23 11:32 BST by Luke Kenneth Casson Leighton
Modified: 2021-05-22 13:21 BST (History)
4 users (show)

See Also:
NLnet milestone: ---
total budget (EUR) for completion of task and all subtasks: 0
budget (EUR) for this task, excluding subtasks' budget: 0
parent task for budget allocation:
child tasks for budget allocation:
The table of payments (in EUR) for this task; TOML format:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luke Kenneth Casson Leighton 2021-04-23 11:32:32 BST
https://libre-soc.org/openpower/

a number of changes have been made which substitute "Power" for "OpenPOWER". this was a proprietary designation for an older version of the ISA.
Comment 1 Alain D D Williams 2021-05-10 20:32:28 BST
A lot of work done on this.

I hope that I have not broken too much :-(

It is not just contents of files but file names, eg openpower -> power.

It is not just a simple search replace as the 'OpenPOWER' foundation name is still that.

web site, maybe redirect http://libre-soc.org/openpower/ -> http://libre-soc.org/power/

Not changed things like:
https://docs.libre-soc.org/openpower-isa/
<https://git.libre-soc.org/?p=libreriscv.git;a=blob;f=openpower/sv_analysis.py;hb=HEAD>
Comment 2 Jacob Lifshay 2021-05-10 20:52:14 BST
(In reply to Alain D D Williams from comment #1)
> It is not just a simple search replace as the 'OpenPOWER' foundation name is
> still that.

maybe search/replace can get you most the way:
s/\bpower\b/openpower/g; s/\bP[oO][wW][eE][rR]\b/OpenPower/g
Comment 3 Alain D D Williams 2021-05-10 21:04:13 BST
No, unfortunately, global search/replace will not work ... there are just far too many exceptions
Comment 4 Luke Kenneth Casson Leighton 2021-05-10 21:48:49 BST
ah, right.  the idea was to *restore* the mistaken replacement of
the word "OpenPOWER" with the word "POWER", rather than "continue
the process of removing the word OpenPOWER and replacing it with
the word POWER".

i've performed a force-master-push reverting the changes, and have
locked everybody out of the git repository who has write-access.

this is because if anyone tries to commit on top of the mistaken
master branch, it will cause massive confusion and corruption of
the git repository.

if it was only one or two files i would have simply reverted the
change.  50+ files, it's best to force-master-push.


one of the reasons why the name may not be changed is because i have
already made public announcements pointing to the directory
https://libre-soc.org/openpower, and, also there is an "underlay"
on the wiki pages with the openpower-isa contents.

alain you have write access to the gitolite-admin repository, can
i leave it with you to confirm that nobody else has checked out the
repository beyond this location:

https://git.libre-soc.org/?p=libreriscv.git;a=commit;h=8a91162a27411d4f932363cf36e7da99aff9f8f6

if they have, they will need to either:

* DESTROY their checked out copy of the repository     OR
* RENAME the master branch to point to the new master
  8a91162a27411d4f932363cf36e7da99aff9f8f6

and only then, once they have informed you of that, then AND ONLY
then should their name be re-added to the gitolite-admin conf
file, in this section:

repo libreriscv
    RW+     =   admin adminbigmac
    R       =   @all

that includes yourself: you should *ALSO* destroy the current checked
out copy of the repo or rename your local master branch, and only
then re-add yourself to the "RW+" list of users for the libreriscv
repository.

anyone who has NOT done a "git pull" since 
Mon, 10 May 2021 18:23:01 +0100 (18:23 +0100)
will be absolutely fine.  they will *NOT* need to destroy their checked
out repository or perform the manual master branch rename.
Comment 5 Jacob Lifshay 2021-05-11 00:35:28 BST
(In reply to Luke Kenneth Casson Leighton from comment #4)
> anyone who has NOT done a "git pull" since 
> Mon, 10 May 2021 18:23:01 +0100 (18:23 +0100)
> will be absolutely fine.

I'm fine then, assuming you got the right date. (wasn't this bug opened in april?)
Comment 6 Luke Kenneth Casson Leighton 2021-05-20 16:15:25 BST
excellent, re-added you jacob.  also veera has confirmed he did not
git pull during that period: re-adding him as well.
Comment 7 Cesar Strauss 2021-05-22 13:21:08 BST
comment #4)
> i've performed a force-master-push reverting the changes, and have
> locked everybody out of the git repository who has write-access.

I've checked, and I'm good.