linux-kernel - Re: [PATCH] Documentation: remove outdated references to the linux-next wiki

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Aug 2014 06:05:58 +0900
From:	SeongJae Park <sj38.park@...il.com>
To:	Jim Davis <jim.epost@...il.com>, frank@...eidel.de
Cc:	rdunlap@...radead.org, linux-doc@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Greg KH <gregkh@...uxfoundation.org>, sfr@...b.auug.org.au
Subject: Re: [PATCH] Documentation: remove outdated references to the
 linux-next wiki

On Thu, Aug 21, 2014 at 5:29 AM, Jim Davis <jim.epost@...il.com> wrote:
> The linux-next wiki at http://linux.f-seidel.de/linux-next/pmwiki has
> been gone for several months now.

Yes, I can't load the page, too. BTW, wouldn't it be better to add
Frank Seidel as recipient because he was the manager of the wiki?

I added him as this mail's recipient.

Thank.

>
> Signed-off-by: Jim Davis <jim.epost@...il.com>
> ---
>  Documentation/HOWTO                            | 1 -
>  Documentation/development-process/2.Process    | 4 ----
>  Documentation/development-process/8.Conclusion | 4 ----
>  3 files changed, 9 deletions(-)
>
> diff --git a/Documentation/HOWTO b/Documentation/HOWTO
> index 57cf5efb044d..93aa8604630e 100644
> --- a/Documentation/HOWTO
> +++ b/Documentation/HOWTO
> @@ -324,7 +324,6 @@ tree, they need to be integration-tested.  For this purpose, a special
>  testing repository exists into which virtually all subsystem trees are
>  pulled on an almost daily basis:
>         http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git
> -       http://linux.f-seidel.de/linux-next/pmwiki/
>
>  This way, the -next kernel gives a summary outlook onto what will be
>  expected to go into the mainline kernel at the next merge period.
> diff --git a/Documentation/development-process/2.Process b/Documentation/development-process/2.Process
> index 2e0617936e8f..c24e156a6118 100644
> --- a/Documentation/development-process/2.Process
> +++ b/Documentation/development-process/2.Process
> @@ -289,10 +289,6 @@ lists when they are assembled; they can be downloaded from:
>
>         http://www.kernel.org/pub/linux/kernel/next/
>
> -Some information about linux-next has been gathered at:
> -
> -       http://linux.f-seidel.de/linux-next/pmwiki/
> -
>  Linux-next has become an integral part of the kernel development process;
>  all patches merged during a given merge window should really have found
>  their way into linux-next some time before the merge window opens.
> diff --git a/Documentation/development-process/8.Conclusion b/Documentation/development-process/8.Conclusion
> index 1990ab4b4949..caef69022e9c 100644
> --- a/Documentation/development-process/8.Conclusion
> +++ b/Documentation/development-process/8.Conclusion
> @@ -22,10 +22,6 @@ Beyond that, a valuable resource for kernel developers is:
>
>         http://kernelnewbies.org/
>
> -Information about the linux-next tree gathers at:
> -
> -       http://linux.f-seidel.de/linux-next/pmwiki/
> -
>  And, of course, one should not forget http://kernel.org/, the definitive
>  location for kernel release information.
>
> --
> 2.1.0
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/