* maintaining.texi (Branches): Remove text copied from other sources.

diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index 9361ae19a57119fe7a82d78e7dccff428337f0e0..079f6f01d9d37ed79dedf5beb0b595bcf5098f5b 100644 (file)
--- a/doc/emacs/ChangeLog
+++ b/doc/emacs/ChangeLog
@@ -1,3 +1,8 @@
+2013-06-07  Xue Fuqiao  <xfq.free@gmail.com>
+
+       * maintaining.texi (Branches): Remove text copied from other
+       sources.
+
 2013-06-05  Alan Mackenzie  <acm@muc.de>
 
        * search.texi (Isearch Scroll): Rename to "Not Exiting Isearch".

diff --git a/doc/emacs/maintaining.texi b/doc/emacs/maintaining.texi
index 17c04fe74e35477f77158e6d324c1296afa51608..dbcd08ee017a6154e93318bb33cc76fcea6ed65f 100644 (file)
--- a/doc/emacs/maintaining.texi
+++ b/doc/emacs/maintaining.texi
@@ -1267,16 +1267,7 @@ bring them back at a later time).
 @cindex branch (version control)
 
   One use of version control is to support multiple independent lines
-of development, which are called @dfn{branches}.  Branches allow for
-parts of software to be developed in parallel.  Large projects require
-many roles to be filled, including developers, build managers, and
-quality assurance personnel. Further, multiple releases on different
-operating system platforms may have to be maintained.  Branches allow
-contributors to isolate changes without destabilizing the codebase,
-for example, fixes for bugs, new features, and versions
-integration. These changes may be later merged (resynchronized) after
-testing.
-
+of development, which are called @dfn{branches}.
 
   VC's support for branch operations is currently fairly limited.  For
 decentralized version control systems, it provides commands for