Temporary changes regarding btrfs branch in linux-next and development patches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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/
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux