From: Dave Airlie <airlied@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Dave Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, torvalds@osdl.org,
jonsmirl@gmail.com
Subject: Re: lindenting the drm directory..
Date: Sat, 8 Jan 2005 16:50:09 +1100 [thread overview]
Message-ID: <21d7e99705010721504365d373@mail.gmail.com> (raw)
In-Reply-To: <20050107211002.3f86d325.akpm@osdl.org>
> It's probably best that you wait until the tree is in good shape and stable
> for a week or two before doing the big reformat because it will introduce a
> barrier over which patches may not pass in either direction.
well as most patches come via the CVS tree and myself it shouldn't be
too bad, the CVS tree has been Lindented for a couple of months so
I've been dealing with the issues myself as I pass the patches back
and forth...
Dave.
prev parent reply other threads:[~2005-01-08 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 4:15 lindenting the drm directory Dave Airlie
2005-01-08 5:10 ` Andrew Morton
2005-01-08 5:50 ` Dave Airlie [this message]
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=21d7e99705010721504365d373@mail.gmail.com \
--to=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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