From: Domen Puncer <domen@coderock.org>
To: Jesse Millan <jessem@cs.pdx.edu>
Cc: kj <kernel-janitors@lists.osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [KJ] 2.6.13-rc2-kj (Should work now, was: (Broken Link))
Date: Wed, 06 Jul 2005 21:19:43 +0000 [thread overview]
Message-ID: <20050706211943.GA27151@homer.coderock.org> (raw)
In-Reply-To: <42CC3C34.8050302@cs.pdx.edu>
[-- Attachment #1: Type: text/plain, Size: 80 bytes --]
That's what happens if you close the console with reminder to copy. :-)
Domen
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
WARNING: multiple messages have this Message-ID (diff)
From: Domen Puncer <domen@coderock.org>
To: Jesse Millan <jessem@cs.pdx.edu>
Cc: kj <kernel-janitors@lists.osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [KJ] 2.6.13-rc2-kj (Should work now, was: (Broken Link))
Date: Wed, 6 Jul 2005 23:19:43 +0200 [thread overview]
Message-ID: <20050706211943.GA27151@homer.coderock.org> (raw)
In-Reply-To: <42CC3C34.8050302@cs.pdx.edu>
That's what happens if you close the console with reminder to copy. :-)
Domen
next prev parent reply other threads:[~2005-07-06 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 20:00 [KJ] 2.6.13-rc2-kj Domen Puncer
2005-07-06 20:00 ` 2.6.13-rc2-kj Domen Puncer
2005-07-06 20:16 ` [KJ] 2.6.13-rc2-kj (Broken Link) Jesse Millan
2005-07-06 20:16 ` Jesse Millan
2005-07-06 21:19 ` Domen Puncer [this message]
2005-07-06 21:19 ` [KJ] 2.6.13-rc2-kj (Should work now, was: (Broken Link)) Domen Puncer
2005-07-06 20:52 ` [KJ] 2.6.13-rc2-kj Tobias Klauser
2005-07-06 21:21 ` Domen Puncer
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=20050706211943.GA27151@homer.coderock.org \
--to=domen@coderock.org \
--cc=jessem@cs.pdx.edu \
--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.