All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Colin McCabe <cmccabe@alumni.cmu.edu>
Cc: Project Hail List <hail-devel@vger.kernel.org>,
	Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: [PATCH 2/3] cld: Add XDR files to gitignore
Date: Thu, 04 Feb 2010 17:30:30 -0500	[thread overview]
Message-ID: <4B6B4A86.4090909@garzik.org> (raw)
In-Reply-To: <1265283057-30884-2-git-send-email-cmccabe@alumni.cmu.edu>

On 02/04/2010 06:30 AM, Colin McCabe wrote:
> Signed-off-by: Colin McCabe<cmccabe@alumni.cmu.edu>
> ---
>   .gitignore |    4 ++++
>   1 files changed, 4 insertions(+), 0 deletions(-)

While patch #1 seems OK at first glance, patches 2 and 3 definitely 
belong in the big XDR patch, because they refer to things not yet in the 
tree.

Cosmetic patches breaking lines or moving code around are fine, in 
preparation for an upcoming patch.  Those can be thought of as logically 
separate from the big XDR patch, even if they are -preparing- for said 
patch.  For example, I am thinking that the next move might be to move 
existing code into smaller functions as you did -- ie. accept_seqid() -- 
while still keeping the existing, pre-XDR code logic.  That makes the 
diff smaller, easier to read and review, while not specifically doing 
anything XDR related.

	Jeff



  reply	other threads:[~2010-02-04 22:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04 11:30 [PATCH 1/3] cld: Create cldc_call_opts_get_data API for GET Colin McCabe
2010-02-04 11:30 ` [PATCH 2/3] cld: Add XDR files to gitignore Colin McCabe
2010-02-04 22:30   ` Jeff Garzik [this message]
2010-02-04 11:30 ` [PATCH 3/3] cld: Add XDR support to lib/Makefile.am Colin McCabe
2010-02-04 23:52 ` [PATCH 1/3] cld: Create cldc_call_opts_get_data API for GET Jeff Garzik

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=4B6B4A86.4090909@garzik.org \
    --to=jeff@garzik.org \
    --cc=cmccabe@alumni.cmu.edu \
    --cc=hail-devel@vger.kernel.org \
    --cc=zaitcev@redhat.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 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.