From: Kumba <kumba@gentoo.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Mailing patches
Date: Mon, 04 Jun 2007 23:54:35 -0400 [thread overview]
Message-ID: <4664DE7B.6070701@gentoo.org> (raw)
In-Reply-To: <4664DB12.80906@gentoo.org>
Kumba wrote:
>
> What about just attaching the patches to a message? Seems like it'll
> avoid most of the problems Tbird has with them. I'm just not sure if
> that hampers importing them into git or not.
>
>
> --Kumba
Deeerrr...
> 6) No MIME, no links, no compression, no attachments. Just plain text.
# dd if=/dev/coffee of=/proc/self/root cpc=135 count=2
2+0 cups in
2+0 cups out
270 milligrams (0.2 g) drank, 0 s, Infinity C/s
--Kumba
--
Gentoo/MIPS Team Lead
"Such is oft the course of deeds that move the wheels of the world: small hands
do them because they must, while the eyes of the great are elsewhere." --Elrond
next prev parent reply other threads:[~2007-06-05 3:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 13:35 Mailing patches Ralf Baechle
2007-06-05 3:40 ` Kumba
2007-06-05 3:54 ` Kumba [this message]
2007-06-05 15:24 ` Ralf Baechle
2007-06-05 15:23 ` Ralf Baechle
2007-06-06 5:09 ` Tian
2007-06-06 6:33 ` Franck Bui-Huu
2007-06-06 7:24 ` Tian
2007-06-06 7:48 ` Franck Bui-Huu
2007-06-06 16:58 ` Ralf Baechle
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=4664DE7B.6070701@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox