[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs branches in git

From: Xue Fuqiao
Subject: Re: Emacs branches in git
Date: Tue, 18 Feb 2014 06:51:27 +0800
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Dmitry Gutov <address@hidden> writes:

> As far as I'm concerned, it subverts the meaning of "master". That's
> just one opinion, though.

In the famous "Pro Git"[fn:1]:

  Many Git developers have a workflow that embraces this approach, such
  as having only code that is entirely stable in their `master' branch —
  possibly only code that has been or will be released. They have
  another parallel branch named develop or next that they work from or
  use to test stability — it isn’t necessarily always stable, but
  whenever it gets to a stable state, it can be merged into `master'.
  You can keep doing this for several levels of stability. Some larger
  projects also have a `proposed' or `pu' (proposed updates) branch that
  has integrated branches that may not be ready to go into the `next' or
  `master' branch. The idea is that your branches are at various levels
  of stability; when they reach a more stable level, they’re merged into
  the branch above them.


[fn:1] http://git-scm.com/book/en/Git-Branching-Branching-Workflows


reply via email to

[Prev in Thread] Current Thread [Next in Thread]