From: Dave Airlie <airlied@linux.ie>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [git tree] DRM fixes/cleanups tree
Date: Sat, 9 Jul 2005 12:46:22 +0100 (IST) [thread overview]
Message-ID: <Pine.LNX.4.58.0507091245330.6297@skynet> (raw)
In-Reply-To: <20050709120947.D2175@flint.arm.linux.org.uk>
>
> Can folk consider using the -p argument to diffstat to obtain the full
> path to the file from the kernels top directory please?
>
> Consider the case where you modify just a Kconfig or Makefile. What
> use does a diffstat showing that just one Makefile or Kconfig somewhere
> in the kernel tree was modified, but not where it was?
Will do in future...
Granted in this case it should be obviously be the drm ones as I usually
stay in my own directory, but I can see your point...
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
Linux kernel - DRI, VAX / pam_smb / ILUG
prev parent reply other threads:[~2005-07-09 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 11:04 Dave Airlie
2005-07-09 11:09 ` Russell King
2005-07-09 11:46 ` 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=Pine.LNX.4.58.0507091245330.6297@skynet \
--to=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--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
all inboxes | Powered by JetHome®