summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2019-09-03 11:34:09 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2019-09-05 13:40:31 +0200
commit31e1bbd1cab7f27c60493938a0fd5d9f51ce7cd8 (patch)
treed5c14508f11585e0564784ca6d67c9d2bf8c0726
parentf06530d86ba7688067fc2758b5e54599bda1e4a0 (diff)
downloadsystemd-31e1bbd1cab7f27c60493938a0fd5d9f51ce7cd8.tar.gz
docs: fix push recipe in RELEASE.md
-rw-r--r--docs/RELEASE.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/RELEASE.md b/docs/RELEASE.md
index d842afcd34..56debd68d2 100644
--- a/docs/RELEASE.md
+++ b/docs/RELEASE.md
@@ -16,4 +16,4 @@ title: Steps to a Successful Release
10. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
11. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
12. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released`)
-13. [After final release] Also push commits to stable, create an empty -stable branch: `git push systemd-stable origin/master:master origin/master:v${version}-stable`, and change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).
+13. [After final release] Also push commits to stable, create an empty -stable branch: `git push systemd-stable origin/master:master origin/master:refs/heads/${version}-stable`, and change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).