From: Daniel Phillips <phillips@istop.com>
To: Dave Jones <davej@redhat.com>
Cc: kernel-mentors@selenic.com, netdev <netdev@vger.kernel.org>
Subject: Re: argh... ;/
Date: Sat, 6 Aug 2005 04:56:34 +1000 [thread overview]
Message-ID: <200508060456.34616.phillips@istop.com> (raw)
In-Reply-To: <20050805174946.GK2241@redhat.com>
On Saturday 06 August 2005 03:49, Dave Jones wrote:
> On Fri, Aug 05, 2005 at 01:20:59PM -0400, John W. Linville wrote:
> > 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.
>
> Indeed. Replying to such mails ends up looking like..
>
Hi, sorry, about the misfired "test" mail... the _real_ issue for me was that
Kmail was turning tabs into spaces for the longest time, so forcing me either
to switch mailers (and you know how appealing that is) or send patches as
attachments. It's finally fixed, so I'll happily join in with dumping on the
poor misguided folks who insist on posting their patches as attachments.
Regards,
Daniel "the flexible" Phillips
next prev parent reply other threads:[~2005-08-05 18:56 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
2005-08-05 17:45 ` Jeff Garzik
2005-08-05 17:49 ` Dave Jones
2005-08-05 18:56 ` Daniel Phillips [this message]
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=200508060456.34616.phillips@istop.com \
--to=phillips@istop.com \
--cc=davej@redhat.com \
--cc=kernel-mentors@selenic.com \
--cc=netdev@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 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).