Copyleft/guide Changeset - cd25fdd2c919

Changeset - cd25fdd2c919

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Bradley Kuhn (bkuhn) - 9 years ago 2014-12-21 00:34:05
bkuhn@ebb.org

Document work-around for 'next' branch rebases.

Upstream in the copyleft.org tutorial repository, the next branch is
sometimes rebased against the master branch. (For example, this occurs
when there have been quick fixes done on 'master' while new drafting
occurs on 'next'.)

This procedure, while convoluted, is the best way I've found to
compensate for this problem. Hosting sites like Gitorious really aren't
designed for rebased branches.

1 file changed with 18 insertions and 5 deletions:

CONTRIBUTING.md

0 comments (0 inline, 0 general)

CONTRIBUTING.md

➞

Show inline comments

@@ ... / @@ -125,17 +125,30 @@ request. @@
 . First, ensure the Git repository points at the right branch and all old
    changes are committed.
         $ git checkout official-next
         $ git pull copyleft-tutorial-official
         $ git status
    The output of the last command should look like this:
-        # On branch official-next
+        # On branch SOME_BRANCH
         nothing to commit (working directory clean)
    If you don't get that output, you probably have uncommitted changes, which
    is beyond the scope of this tutorial.
    If you don't get that output, you probably have uncommitted changes from
    some other situation, which is beyond the scope of this document.
 . Now, get the most recent version of the 'next' branch:
         $ git checkout master
         $ git branch -D official-next
         $ git fetch copyleft-tutorial-official
         $ git branch --track official-next copyleft-tutorial-official/next
         $ git checkout official-next
         $ git pull
    (This step is more complicated than is typically found in a tutorial like
    this.  Experienced Git users will note the above is the easiest way to
    handle the fact that the 'next' branch is occasionally rebased against
    master.  If 'next' branch has not been rebased since the last time the
    operation was performed, the last two commands suffice for this step.)
 . Next, create a new branch to hold your changes:

0 comments (0 inline, 0 general)