[PATCH] Documentation: clarify that patches should target the master branch.

Robert Schwebel r.schwebel at pengutronix.de
Thu Sep 22 10:14:22 PDT 2016

I asked Sascha if he still prefers patches against 'next', and it turned
out that this is not true any more and patches should be sent against

Signed-off-by: Robert Schwebel <r.schwebel at pengutronix.de>
 Documentation/user/barebox.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/Documentation/user/barebox.rst b/Documentation/user/barebox.rst
index 32cec3d..1203c10 100644
--- a/Documentation/user/barebox.rst
+++ b/Documentation/user/barebox.rst
@@ -28,9 +28,11 @@ can be checked out as follows:
   Checking connectivity... done.
   Checking out files: 100% (5651/5651), done.
-After this, make sure to check out the appropriate branch. If you want to
-develop for barebox, it's best to check out the ``next`` branch rather than
-the ``master`` branch:
+By default, the master branch is checked out. If you want to develop for
+barebox, this is the right branch to send patches against.
+If you want to see which patches are already selected for the next release,
+you can look at the ``next`` branch:
 .. code-block:: sh

More information about the barebox mailing list