|
|
Question Removed Member on 3
~R@JEES#
|
|
|
|
|
10th kick applied.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
|
Last Kick Applied. Gone
~R@JEES#
|
|
|
|
|
|
|
This[^] taken from here[^]
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Member and Article Gone
~R@JEES#
|
|
|
|
|
|
Unbelievable!
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
|
Hard to believe that Mr. Maunder would be a co-author in this[^]
|
|
|
|
|
I think it's possible to add co-authors without they have to confirm. However, looking at that, I believe it would be a good idea to require confirmation from the co-author before they're added.
The quick red ProgramFOX jumps right over the Lazy<Dog> .
|
|
|
|
|
I just posted a comment stating my doubts about Chris being involved in this.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
|
|
|
|
|
Remember this: [^]
An author can add co-authors by knowing the member id...But IIRC, the co-author notified of it...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Yep, I do remember
I posted this since IMO this feels like abuse...
|
|
|
|
|
I agree.
I reported both authors, to be on the safe side...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: I reported both authors
Didn't feel that was necessary. I reported just the first one
|
|
|
|
|
|
|
I think he tripped on the wire and went straight out of CP. Pity...
Geek code v 3.12
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++*
Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I think he might have received a more sympathetic hearing if he had actually taken note of OriginalGriff's comments, and pulled his articles for reworking.
|
|
|
|
|
|