From: Christoph Hellwig <hch@infradead.org>
To: Felix Blyakher <felixb@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs:move fsr over from xfsdump
Date: Fri, 23 Jan 2009 22:26:38 -0500 [thread overview]
Message-ID: <20090124032638.GB14080@infradead.org> (raw)
In-Reply-To: <133A2143-EFC5-4D09-BF73-5C32B14C5C47@sgi.com>
On Fri, Jan 23, 2009 at 01:06:16AM -0600, Felix Blyakher wrote:
> Christoph,
>
> There are several whitespace warnings while applying this patch:
It's really just moving over the code, no need for whitespace cleanups.
Especially not in userspace code where we don't have the whitespace
policy on our kneck..
> /data/lwork/attica1/felixb/xfscmds-git/xfsprogs/.git/rebase-apply/
> patch:1632: space before tab in indent.
Btw, I'd _really_ prefer just apply my patches myself to the shared
commit development tree and not recreating the previous bottleneck.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-01-24 3:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 0:33 [PATCH] xfsprogs:move fsr over from xfsdump Christoph Hellwig
2009-01-23 7:06 ` Felix Blyakher
2009-01-24 3:26 ` Christoph Hellwig [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=20090124032638.GB14080@infradead.org \
--to=hch@infradead.org \
--cc=felixb@sgi.com \
--cc=xfs@oss.sgi.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