From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Btrfs-convert: Add support to copy common inode flags
Date: Fri, 14 Oct 2016 08:50:31 +0800 [thread overview]
Message-ID: <41c42235-ef89-1f5c-28cc-bf3275045737@cn.fujitsu.com> (raw)
In-Reply-To: <20161013141558.GW11398@twin.jikos.cz>
At 10/13/2016 10:15 PM, David Sterba wrote:
> Hi,
>
> patches merged to devel, thanks. I made a few minor adjustments, not
> bothering you with them.
Thanks for all your work.
Now I can just rebase my scrub work to devel branch.
>
> On Tue, Oct 11, 2016 at 10:44:42AM +0800, Qu Wenruo wrote:
>> Branch can be fetched from:
>> https://github.com/adam900710/btrfs-progs/tree/convert_inode_flags
>
> I can pull the branches from you, either to devel or integration. Please
> base them on the last release point (ie. master) if there are no other
> dependencies. Otherwise, I'll publish a branch that contains the desired
> patches and will promise not to change it with rebases.
>
Sorry I'm not very familiar with when to send a pull request and when to
send normal patches, and to which branch it should be rebased to.
From my understanding, for large patchset pull request is preferred(and
patchse should still be sent out for review) and for small changes,
normal mail should be good enough.
And normally I rebase all my branches/patches to your devel branch.
Or should I rebase them to the master branch?
Thanks,
Qu
next prev parent reply other threads:[~2016-10-14 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 2:44 [PATCH v2 0/4] Btrfs-convert: Add support to copy common inode flags Qu Wenruo
2016-10-11 2:44 ` [PATCH v2 1/4] btrfs-progs: Copy btrfs inode flags from kernel header Qu Wenruo
2016-10-11 2:44 ` [PATCH v2 2/4] btrfs-progs: Make btrfs-debug-tree print all readable strings for inode flags Qu Wenruo
2016-10-11 2:44 ` [PATCH v2 3/4] btrfs-progs: convert: Convert ext inode flags to btrfs " Qu Wenruo
2016-10-11 2:44 ` [PATCH v2 4/4] btrfs-progs: convert-test: Add test case for common " Qu Wenruo
[not found] ` <20161013141558.GW11398@twin.jikos.cz>
2016-10-14 0:50 ` Qu Wenruo [this message]
2016-10-14 14:57 ` [PATCH v2 0/4] Btrfs-convert: Add support to copy " David Sterba
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=41c42235-ef89-1f5c-28cc-bf3275045737@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.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 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.