From: Jon Loeliger <jdl@freescale.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Jon Loeliger <jdl@jdl.com>
Subject: Re: dtc: Add testcases for tree checks
Date: Tue, 20 Nov 2007 16:22:34 -0600 [thread overview]
Message-ID: <1195597354.25887.39.camel@ld0161-tx32> (raw)
In-Reply-To: <20071120220309.GB13156@localhost.localdomain>
On Tue, 2007-11-20 at 16:03, David Gibson wrote:
> Well, yes. But, IMO, every time anyone other that you or I has
> commented on one of these patches as it goes past counts as an
> occasion when it's better that I've been using patches, rather than
> pushing to you direct with git.
I am not asking you to stop sending patches.
I'm asking you to generate your patches with git.
Git's patch format, send through mail, handles
the execute permissions.
> Actually, that should be possible with mails too, it's just that I
> forgot the --- line.
Right. I'm just asking for it to be used. :-)
jdl
next prev parent reply other threads:[~2007-11-20 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 5:24 dtc: Add testcases for tree checks David Gibson
2007-11-20 15:09 ` Jon Loeliger
2007-11-20 22:03 ` David Gibson
2007-11-20 22:22 ` Jon Loeliger [this message]
2007-11-20 22:23 ` Scott Wood
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=1195597354.25887.39.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=david@gibson.dropbear.id.au \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.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