linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org
Subject: Temporary changes regarding btrfs branch in linux-next and development patches
Date: Mon, 3 Jul 2017 16:21:08 +0200	[thread overview]
Message-ID: <20170703142108.GZ2866@suse.cz> (raw)

Hi,

in order to allow merging new btrfs patches and also keep linux-next merging
sane [1], I'm going to freeze any changes to my k.org [2] branch for-next until
4.13-rc1 is released, expecting that the conflicting branches get merged as
well.

* k.org for-next will contain only the upcoming pull request
  (top commit 848c23b78fafdcd3270b06a30737f8dbd70c347f)
* k.org for-next-test will gather patches and patchsets from mailinglist as usual

[1] https://marc.info/?l=linux-next&m=149904517832129
[2] https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git/

             reply	other threads:[~2017-07-03 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 14:21 David Sterba [this message]
2017-07-14 14:31 ` Temporary changes regarding btrfs branch in linux-next and development patches 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=20170703142108.GZ2866@suse.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).