From: Dan Merillat <dan.merillat@gmail.com>
To: David Sterba <dsterba@suse.cz>, btrfs <linux-btrfs@vger.kernel.org>
Subject: [PATCH 0/3] btrfs-progs: restore symlinks
Date: Thu, 23 Apr 2015 12:47:29 -0400 [thread overview]
Message-ID: <55392221.6090502@gmail.com> (raw)
Hopefully this is sufficiently paranoid, tested with PATH_MAX length
symlinks, existing files, insufficient permissions, dangling symlinks.
I think I got the coding style correct this time, I'll fix and resend if
not.
Includes a trivial fix from my metadata patch, the documentation got
lost in the merge.
next reply other threads:[~2015-04-23 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 16:47 Dan Merillat [this message]
2015-04-23 16:50 ` [PATCH 1/3] btrfs-progs: restore: document metadata restore Dan Merillat
2015-04-23 16:51 ` [PATCH 2/3] btrfs-progs: separate the overwrite check Dan Merillat
2015-04-24 15:24 ` David Sterba
2015-04-25 18:19 ` Dan Merillat
2015-04-29 15:38 ` David Sterba
2015-04-23 16:52 ` [PATCH 3/3] btrfs-progs: optionally restore symlinks Dan Merillat
2015-04-24 4:38 ` [PATCH 0/3] btrfs-progs: " Duncan
2015-04-25 18:16 ` Dan Merillat
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=55392221.6090502@gmail.com \
--to=dan.merillat@gmail.com \
--cc=dsterba@suse.cz \
--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).