Changeset - 81157b31366a
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 9 years ago 2014-12-21 00:31:57
bkuhn@ebb.org
No instructions for 'master';just note possibility

Ultimately, users will probably pick either 'master' or 'next' to submit
changes anyway, so just leave the instructions to refer to 'next' and
note that they could replace 'next' with 'master'.
1 file changed with 4 insertions and 1 deletions:
0 comments (0 inline, 0 general)
CONTRIBUTING.md
Show inline comments
...
 
@@ -86,6 +86,10 @@ are not necessarily rejected.  In fact, if your change is a fix for typo,
 
spelling, grammar, formatting or anything urgent, submitting a patch against
 
'master' may make more sense.
 

	
 
To use the instructions below for proposals against the 'master' branch, just
 
replace 'next' everywhere below with 'master'.
 

	
 

	
 
### Contributing via Gitorious
 

	
 
First-time contributors may want to do the following four items first:
...
 
@@ -113,7 +117,6 @@ First-time contributors may want to do the following four items first:
 

	
 
        $ git remote add copyleft-tutorial-official git@gitorious.org:copyleft-org/tutorial.git
 
        $ git fetch copyleft-tutorial-official
 
        $ git branch --track official-master copyleft-tutorial-official/master
 
        $ git branch --track official-next copyleft-tutorial-official/next
 

	
 
That completes the first-time setup.  Next is a workflow each proposed merge
0 comments (0 inline, 0 general)