From: Domen Puncer <domen@coderock.org>
To: kj <kernel-janitors@lists.osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [KJ] 2.6.13-rc1-kj [was 2.6.13-rc1]
Date: Wed, 29 Jun 2005 13:17:52 +0000 [thread overview]
Message-ID: <20050629131752.GI3904@nd47.coderock.org> (raw)
In-Reply-To: <20050629131351.GH3904@nd47.coderock.org>
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
No, no... I didn't took Linus' job ;-)
The correct subject is: 2.6.13-rc1-kj
On 29/06/05 15:13 +0200, Domen Puncer wrote:
> A new release from kernel janitors (http://janitor.kernelnewbies.org/).
>
>
> Patchset is at http://coderock.org/kj/2.6.13-rc1-kj/
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
WARNING: multiple messages have this Message-ID (diff)
From: Domen Puncer <domen@coderock.org>
To: kj <kernel-janitors@lists.osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: 2.6.13-rc1-kj [was 2.6.13-rc1]
Date: Wed, 29 Jun 2005 15:17:52 +0200 [thread overview]
Message-ID: <20050629131752.GI3904@nd47.coderock.org> (raw)
In-Reply-To: <20050629131351.GH3904@nd47.coderock.org>
No, no... I didn't took Linus' job ;-)
The correct subject is: 2.6.13-rc1-kj
On 29/06/05 15:13 +0200, Domen Puncer wrote:
> A new release from kernel janitors (http://janitor.kernelnewbies.org/).
>
>
> Patchset is at http://coderock.org/kj/2.6.13-rc1-kj/
next prev parent reply other threads:[~2005-06-29 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 13:13 [KJ] 2.6.13-rc1 Domen Puncer
2005-06-29 13:13 ` 2.6.13-rc1 Domen Puncer
2005-06-29 13:17 ` Domen Puncer [this message]
2005-06-29 13:17 ` 2.6.13-rc1-kj [was 2.6.13-rc1] Domen Puncer
2005-06-29 16:26 ` [KJ] 2.6.13-rc1 Alexey Dobriyan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050629131752.GI3904@nd47.coderock.org \
--to=domen@coderock.org \
--cc=kernel-janitors@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.