From: Goffredo Baroncelli <kreijack@libero.it>
To: Chris Samuel <chris@csamuel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Removing btrfsctl, btrfs-vol, btrfs-show
Date: Sun, 10 Jun 2012 22:49:03 +0200 [thread overview]
Message-ID: <4FD5083F.5010901@libero.it> (raw)
In-Reply-To: <201206101846.41496.chris@csamuel.org>
On 06/10/2012 10:46 AM, Chris Samuel wrote:
> On Saturday 09 June 2012 16:24:19 Goffredo Baroncelli wrote:
>
>> This commit removes all the related code.
>
> This doesn't seem to apply cleanly with patch
Did you pass the "-p1" switch to the patch command ?
> (though git am
> seems to apply it OK) to the git repo master from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git
>
> FYI patch complains thus:
>
> patching file INSTALL
> patching file Makefile
> patching file btrfs-show.c
> patching file btrfs-vol.c
> patching file btrfsctl.c
> patching file Makefile
> Hunk #1 FAILED at 6.
> Hunk #2 FAILED at 17.
> 2 out of 2 hunks FAILED -- saving rejects to file Makefile.rej
> patching file btrfs-image.8.in
> Hunk #1 FAILED at 31.
> 1 out of 1 hunk FAILED -- saving rejects to file btrfs-image.8.in.rej
> The next patch would delete the file btrfs-show.8.in,
> which does not exist! Assume -R? [n]
> Apply anyway? [n]
> Skipping patch.
> 1 out of 1 hunk ignored
> patching file btrfsck.8.in
> Hunk #1 FAILED at 14.
> 1 out of 1 hunk FAILED -- saving rejects to file btrfsck.8.in.rej
> The next patch would delete the file btrfsctl.8.in,
> which does not exist! Assume -R? [n]
> Apply anyway? [n]
> Skipping patch.
> 1 out of 1 hunk ignored
>
>
prev parent reply other threads:[~2012-06-10 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 6:24 [PATCH][btrfs-progs] Removing btrfsctl, btrfs-vol, btrfs-show Goffredo Baroncelli
2012-06-09 6:24 ` [PATCH] " Goffredo Baroncelli
2012-06-10 8:46 ` Chris Samuel
2012-06-10 20:49 ` Goffredo Baroncelli [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=4FD5083F.5010901@libero.it \
--to=kreijack@libero.it \
--cc=chris@csamuel.org \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
/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).