Skip to contentSkip to conversation

drop linuxppc64-dev

PATCH In review Olaf Hering 3 participants 7 messages Jan 16, 2006 – Jan 18, 2006 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 drop linuxppc64-dev

Everything is merged into arch/powerpc now.
Stop cross-posting.

 Documentation/powerpc/hvcs.txt |    2 +-
 MAINTAINERS                    |    4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)
Documentation/powerpc/hvcs.txt +1 -1
Index: linux-2.6.15-olh/Documentation/powerpc/hvcs.txt
===================================================================
@@ -560,7 +560,7 @@ The proper channel for reporting bugs is
 distribution company that provided your OS or by posting issues to the
 ppc64 development mailing list at:
 
[email protected]
[email protected]
 
 This request is to provide a documented and searchable public exchange
 of the problems and solutions surrounding this driver for the benefit of
MAINTAINERS +2 -2
Index: linux-2.6.15-olh/MAINTAINERS
===================================================================
@@ -527,7 +527,7 @@ S:   Supported
 BROADBAND PROCESSOR ARCHITECTURE
 P:	Arnd Bergmann
 M:	[email protected]
-L:	[email protected]
+L:	[email protected]
 W:	http://linuxppc64.org
 S:	Supported
 
@@ -1606,7 +1606,7 @@ P:	Anton Blanchard
 M:	[email protected]
 M:	[email protected]
 W:	http://linuxppc64.org
-L:	[email protected]
+L:	[email protected]
 S:	Supported
 
 LINUX SECURITY MODULE (LSM) FRAMEWORK
Signature · 2 lines
short story of a lazy sysadmin:
 alias appserv=wotan
#1 lore raw

MAINTAINERS S: Supported · line 532

Quoted 13 lines · Olaf Hering

Everything is merged into arch/powerpc now.
Stop cross-posting.

MAINTAINERS +1 -1
@@ -527,7 +527,7 @@ S:   Supported
 BROADBAND PROCESSOR ARCHITECTURE
 P:     Arnd Bergmann
 M:     [email protected]
-L:     [email protected]
+L:     [email protected]
 W:     http://linuxppc64.org
 S:     Supported

Are you suggesting that nobody should ever use linuxppc64-dev now? If so, patching MAINTAINERS doesn't seem like the right way to enforce that.

Do we want to think about merging the mailing lists? Both seem fairly high-volume right now (compare
http://ozlabs.org/pipermail/linuxppc64-dev/ and
http://ozlabs.org/pipermail/linuxppc-dev/). linuxppc-embedded is separate. There are certainly lots of emails and patches that are common to both 32- and 64-bit, though...

The subscriber lists don't overlap 100%, but the difference might be small enough not to matter to many people.

-Hollis

#2 lore raw
Quoted 3 lines · Hollis Blanchard

Are you suggesting that nobody should ever use linuxppc64-dev now? If so, patching MAINTAINERS doesn't seem like the right way to enforce that.

It felt like a good starting point for this kind of discussion. :-)

Signature · 2 lines
short story of a lazy sysadmin:
 alias appserv=wotan
#3 lore raw
In reply to Olaf Hering
Quoted 9 lines · Olaf Hering

Everything is merged into arch/powerpc now.
Stop cross-posting.

 Documentation/powerpc/hvcs.txt |    2 +-
 MAINTAINERS                    |    4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

[snip]

Quoted 14 lines

Index: linux-2.6.15-olh/MAINTAINERS
===================================================================

MAINTAINERS +1 -1
@@ -527,7 +527,7 @@ S:   Supported
 BROADBAND PROCESSOR ARCHITECTURE
 P:	Arnd Bergmann
 M:	[email protected]
-L:	[email protected]
+L:	[email protected]
 W:	http://linuxppc64.org
 S:	Supported
 

MAINTAINERS P: Anton Blanchard · line 1612

Quoted 8 lines
MAINTAINERS +1 -1
@@ -1606,7 +1606,7 @@ P:	Anton Blanchard
 M:	[email protected]
 M:	[email protected]
 W:	http://linuxppc64.org
-L:	[email protected]
+L:	[email protected]
 S:	Supported
 
 LINUX SECURITY MODULE (LSM) FRAMEWORK

What about the s/linuxppc64\.org/penguinppc\.org/g case? Or is penguinppc64.org preferable? Or am I just taking it too far? ;)

#4 lore raw
Quoted 2 lines · Arthur Othieno

What about the s/linuxppc64\.org/penguinppc\.org/g case? Or is penguinppc64.org preferable? Or am I just taking it too far? ;)

They are redirected on DNS or HTTP level.

Signature · 2 lines
short story of a lazy sysadmin:
 alias appserv=wotan
#5 lore raw
Quoted 6 lines · Olaf Hering
Quoted 2 lines · Arthur Othieno

What about the s/linuxppc64\.org/penguinppc\.org/g case? Or is penguinppc64.org preferable? Or am I just taking it too far? ;)

They are redirected on DNS or HTTP level.

HTTP level, but that doesn't answer his question.

As the maintainer of that site, I would prefer to remove the linuxppc64.org reference.

-Hollis

#6 lore raw

PATCH 1/1 powerpc: replace linuxppc64.org references with penguinppc.org/ppc64/

Quoted 6 lines · Hollis Blanchard
Quoted 5 lines · Olaf Hering
Quoted 2 lines · Arthur Othieno

What about the s/linuxppc64\.org/penguinppc\.org/g case? Or is penguinppc64.org preferable? Or am I just taking it too far? ;)

Quoted 6 lines
Quoted 1 line

They are redirected on DNS or HTTP level.

HTTP level, but that doesn't answer his question.

As the maintainer of that site, I would prefer to remove the linuxppc64.org reference.

[PATCH] powerpc: replace linuxppc64.org references with penguinppc.org/ppc64/

http://www.penguinppc.org/ppc64/ is the canonical URL for all things ppc64.
http://linuxppc64.org is just a redirect so update all references accordingly.

---

Depends on Olaf's: [PATCH] drop linuxppc64-dev

 MAINTAINERS |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

07edae4fcd285140c92dc32229043af1429196ce

MAINTAINERS +2 -2
index 3283304..18dcfb3 100644
@@ -535,7 +535,7 @@ BROADBAND PROCESSOR ARCHITECTURE
 P:	Arnd Bergmann
 M:	[email protected]
 L:	[email protected]
-W:	http://linuxppc64.org
+W:	http://www.penguinppc.org/ppc64/
 S:	Supported
 
 BTTV VIDEO4LINUX DRIVER
@@ -1608,7 +1608,7 @@ M:	[email protected]
 P:	Anton Blanchard
 M:	[email protected]
 M:	[email protected]
-W:	http://linuxppc64.org
+W:	http://www.penguinppc.org/ppc64/
 L:	[email protected]
 S:	Supported
 
Signature · 1 line
1.0.0b