From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [LTP] [PATCH 01/21] lib/parse_opts: STD_LP_sbrk and STD_start_break should only be defined when UCLINUX=0
Date: Wed, 4 Jan 2012 10:27:53 +0000 [thread overview]
Message-ID: <4F0429A9.4070000@imgtec.com> (raw)
In-Reply-To: <CAGH67wTp4qK0ru641QOZx4OiD3=Unie6AP=uMq8J=fpT2=LqBw@mail.gmail.com>
On 01/03/2012 10:17 PM, Garrett Cooper wrote:
> On Tue, Jan 3, 2012 at 12:28 PM, Mike Frysinger<vapier@gentoo.org> wrote:
>> please use `git send-email` to properly post patches. attaching them like
>> this makes it a pita to review.
>
> +1. Or just use what's noted in the style guide as well for submitting
> patches if you really want to go down this path of creating patch
> review/commit request emails.
> Thanks,
> -Garrett
Thanks. I will do that from now on.
--
markos
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-01-04 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 9:16 [LTP] [PATCH 01/21] lib/parse_opts: STD_LP_sbrk and STD_start_break should only be defined when UCLINUX=0 Markos Chandras
2012-01-03 20:28 ` Mike Frysinger
2012-01-03 22:17 ` Garrett Cooper
2012-01-04 10:27 ` Markos Chandras [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=4F0429A9.4070000@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vapier@gentoo.org \
--cc=yanegomi@gmail.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