From: Paul Mackerras <paulus@samba.org>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Please pull from 'for-2.6.24' branch
Date: Tue, 21 Aug 2007 08:55:24 +1000 [thread overview]
Message-ID: <18122.7132.734048.11405@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <46C9BCA8.1070003@freescale.com>
Timur Tabi writes:
> Is this something new that you want done for all patches from now on?
It's not necessary for patches posted to the mailing list, but people
putting commits into a git tree for me to pull need to do it. I have
hacked versions of git-apply{mbox,patch} that do it automatically.
Paul.
next prev parent reply other threads:[~2007-08-20 22:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 13:46 Please pull from 'for-2.6.24' branch Josh Boyer
2007-08-20 4:45 ` Paul Mackerras
2007-08-20 12:33 ` Josh Boyer
2007-08-20 16:09 ` Timur Tabi
2007-08-20 17:40 ` Kumar Gala
2007-08-20 22:55 ` Paul Mackerras [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-14 5:04 Kumar Gala
2007-12-06 19:15 Kumar Gala
2007-11-20 5:56 Kumar Gala
2007-11-20 15:52 ` Kim Phillips
2007-11-09 9:59 Kumar Gala
2007-10-11 14:19 Kumar Gala
2007-09-05 2:07 Olof Johansson
2007-08-23 4:16 Kumar Gala
2007-08-17 7:17 Kumar Gala
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=18122.7132.734048.11405@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.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).