From: "John W. Linville" <linville@tuxdriver.com>
To: Daniel Phillips <phillips@istop.com>
Cc: kernel-mentors@selenic.com, netdev <netdev@vger.kernel.org>
Subject: Re: argh... ;/
Date: Fri, 5 Aug 2005 13:20:59 -0400 [thread overview]
Message-ID: <20050805172055.GB5641@tuxdriver.com> (raw)
In-Reply-To: <200508060241.30507.phillips@istop.com>
On Sat, Aug 06, 2005 at 02:41:30AM +1000, Daniel Phillips wrote:
> On Friday 05 August 2005 13:04, Mateusz Berezecki wrote:
> > I accidentaly posted the patches as MIME attachments... its 5:03 am here
> Does anybody still care if patches are posted as attachments, particularly for
> review as opposed to submission?
Yes. Opening attachments makes them harder to review.
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2005-08-05 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 3:04 argh... ;/ Mateusz Berezecki
2005-08-05 16:41 ` Daniel Phillips
2005-08-05 17:20 ` John W. Linville [this message]
2005-08-05 17:45 ` Jeff Garzik
2005-08-05 17:49 ` Dave Jones
2005-08-05 18:56 ` Daniel Phillips
2005-08-12 5:36 ` Chris Wedgwood
2005-08-12 11:35 ` Ralf Baechle
2005-08-12 11:44 ` John W. Linville
2005-08-12 14:22 ` Chris Wedgwood
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=20050805172055.GB5641@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=kernel-mentors@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=phillips@istop.com \
/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;
as well as URLs for NNTP newsgroup(s).