This is an automated email from Gerrit.

Jerome Forissier (jerome.foriss...@linaro.org) just uploaded a new patch set to 
Gerrit, which you can find at http://openocd.zylin.com/4806

-- gerrit

commit 06b15ea19f7bf94704516397df30ec6a36461b3d
Author: Jerome Forissier <jerome.foriss...@linaro.org>
Date:   Fri Dec 14 16:31:17 2018 +0100

    HACKING: add note about refs/publish/master
    
    The fact that one needs to always push contributions to a single remote
    reference (refs/publish/master) might seem odd to people unfamiliar with
    Gerrit. GitHub, for instance, hosts personal repositories where developers
    typically create topic branches for each contribution and use a proprietary
    mecanism to request a review (the "pull request"). More generally, one
    normally does not expect to be able to push non-fast-forwarding stuff to a
    remote branch.
    
    This commit adds a clarifying note to the patch guidelines.
    
    Change-Id: Ia750b815b82b18e92b6109c07f451000dcbecf9b
    Signed-off-by: Jerome Forissier <jerome.foriss...@linaro.org>

diff --git a/HACKING b/HACKING
index b7ef070..1ff7d80 100644
--- a/HACKING
+++ b/HACKING
@@ -134,6 +134,10 @@ git config remote.review.push HEAD:refs/publish/master
 @code
 git remote add review http://USERNAME:passw...@openocd.zylin.com/p/openocd.git
 @endcode
+  \note All contributions should be pushed to @c refs/publish/master on the
+Gerrit server, even if you plan to use several local branches for different
+topics. It is possible because @c publish/master is not a traditional Git
+branch.
   -# You will need to install this hook, we will look into a better solution:
 @code
 scp -p -P 29418 usern...@openocd.zylin.com:hooks/commit-msg .git/hooks/

-- 


_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to