From 990c84db9d0d4ce1968164d2fcc642a0e2554b68 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonathan=20Neusch=C3=A4fer?= Date: Fri, 30 Nov 2018 15:34:00 +0100 Subject: [PATCH] Documentation: gerrit guidelines: Adopt the new topic syntax MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit When the old syntax is used, gerrit now respends with: remote: WARNING: deprecated topic syntax. Use %topic=TOPIC instead Change-Id: I002bfc3e9c4b348379337bc386d3bdefb307679d Signed-off-by: Jonathan Neuschäfer Reviewed-on: https://review.coreboot.org/c/29983 Reviewed-by: Patrick Georgi Tested-by: build bot (Jenkins) --- Documentation/getting_started/gerrit_guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/getting_started/gerrit_guidelines.md b/Documentation/getting_started/gerrit_guidelines.md index b0a96096e9..ba2b7b9d16 100644 --- a/Documentation/getting_started/gerrit_guidelines.md +++ b/Documentation/getting_started/gerrit_guidelines.md @@ -151,7 +151,7 @@ gerrit. Topics can be set for individual patches in gerrit by going into the patch and clicking on the icon next to the topic line. Topics can also be set when you push the patches into gerrit. For example, to push a set of commits with the i915-kernel-x60 set, use the command: - git push origin HEAD:refs/for/master/i915-kernel-x60 + git push origin HEAD:refs/for/master%topic=i915-kernel-x60 * If one of your patches isn't ready to be merged, make sure it's obvious that you don't feel it's ready for merge yet. The preferred way to show