Re: [Xen-devel] [OSSTEST PATCH] README.dev: Document how to do a force push.

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("[OSSTEST PATCH] README.dev: Document how to do a force 
push."):
> Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
...
> +Force pushing a branch
> +======================
> +
> +As osstest user on test controller
> +$ cd ~/branches/for-$branch.git
> +$ OSSTEST_CONFIG=production-config ./ap-push $branch $revision

This works in ~osstest/testing.git too.

Ian.

From c9cfea3529c7f75b519a861df6457b9d44b167ac Mon Sep 17 00:00:00 2001
From: Ian Campbell <ian.campbell@xxxxxxxxxx>
Date: Tue, 6 Jan 2015 13:51:17 +0000
Subject: [OSSTEST PATCH] README.dev: Document how to do a force push.

Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
---
 README.dev |   13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/README.dev b/README.dev
index eb72659..ed8dcf9 100644
--- a/README.dev
+++ b/README.dev
@@ -123,3 +123,16 @@ initial push works
 When pushing the patches, be sure to make sure that the
 for-$branch.git repo can fast forward to the pushed version (perhaps
 by resetting it).
+
+Force pushing a branch
+======================
+
+As osstest user on test controller
+
+$ cd ~/branches/for-$branch.git
+OR
+$ cd ~/testing.git
+
+$ OSSTEST_CONFIG=production-config ./ap-push $branch $revision
+
+NOTE: $revision must be a revision *not* a tag.
-- 
1.7.10.4


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel