From: Jeff Garzik <jeff@garzik.org>
To: Jim Meyering <jim@meyering.net>
Cc: Project Hail <hail-devel@vger.kernel.org>
Subject: Re: [PATCH tabled 1/2] server/config.c: don't dereference NULL on OOM
Date: Thu, 23 Sep 2010 15:35:53 -0400 [thread overview]
Message-ID: <4C9BAC19.1070407@garzik.org> (raw)
In-Reply-To: <4C9BA847.5030703@garzik.org>
On 09/23/2010 03:19 PM, Jeff Garzik wrote:
> 3) I process patches similar to how Linus and others in the kernel do
> it: "git am /path/to/mbox_of_patches" That tends to impose some
> restrictions on the contents of each email.
FWIW, 'git pull' submissions are welcome. Standard kernel-style pull
submission style applies[1].
Jeff
[1] public git pull URL including branch name, diffstat, shortlog or
full log of changeset summaries, and finally, the combined diff of all
changes.
next prev parent reply other threads:[~2010-09-23 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 8:43 [PATCH tabled 1/2] server/config.c: don't dereference NULL on OOM Jim Meyering
2010-09-23 18:57 ` Jeff Garzik
2010-09-23 19:19 ` Jeff Garzik
2010-09-23 19:35 ` Jeff Garzik [this message]
2010-09-24 11:32 ` Jim Meyering
2010-09-24 11:55 ` Jim Meyering
2010-09-24 17:24 ` Jeff Garzik
2010-09-24 17:43 ` Jim Meyering
2010-09-24 17:50 ` Jeff Garzik
2010-09-24 11:02 ` Jim Meyering
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=4C9BAC19.1070407@garzik.org \
--to=jeff@garzik.org \
--cc=hail-devel@vger.kernel.org \
--cc=jim@meyering.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.