From: Xue Fuqiao <xfq.free@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: changes in r112843
Date: Wed, 5 Jun 2013 07:12:24 +0800 [thread overview]
Message-ID: <CAAF+z6HOwS2BU_LQV_o8+6ct0S1DLj7=in=KG0GO2g4WWGnsxQ@mail.gmail.com> (raw)
In-Reply-To: <CAAF+z6GpDyCgVbMdDxYYWVirPJ=bpNSqqLzmyUUnTtyh1Zdp5w@mail.gmail.com>
On Wed, Jun 5, 2013 at 6:59 AM, Xue Fuqiao <xfq.free@gmail.com> wrote:
> On Wed, Jun 5, 2013 at 1:40 AM, Glenn Morris <rgm@gnu.org> wrote:
>>
>> *** doc/emacs/maintaining.texi 2013-05-30 09:27:55 +0000
>> --- doc/emacs/maintaining.texi 2013-06-02 11:56:39 +0000
>> ***************
>> *** 1266,1275 ****
>> @cindex branch (version control)
>>
>> One use of version control is to support multiple independent lines
>> ! of development, which are called @dfn{branches}. Branches are used
>> ! for maintaining separate ``stable'' and ``development'' versions of a
>> ! program, and for developing unrelated features in isolation from one
>> ! another.
>>
>> VC's support for branch operations is currently fairly limited. For
>> decentralized version control systems, it provides commands for
>> --- 1267,1282 ----
>> @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.
>
>> The new text is copied verbatim from Wikipedia.
>> Please just remove it, since (IMO) the Emacs manual does not need to
>> explain every possible reason why people might want to use branches.
>
> IMHO (at least) this sentence is useful here:
>
> Branches allow contributors to isolate changes without destabilizing the
> codebase, for example, fixes for bugs, new features, and
> versions integration.
Or just only leave the first sentence:
One use of version control is to support multiple independent lines.
Remove the (both versions) motivation of branching.
--
Best regards, Xue Fuqiao.
http://www.gnu.org/software/emacs/
next prev parent reply other threads:[~2013-06-04 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 17:40 changes in r112843 Glenn Morris
2013-06-04 22:59 ` Xue Fuqiao
2013-06-04 23:12 ` Xue Fuqiao [this message]
2013-06-05 10:46 ` Thien-Thi Nguyen
2013-06-05 23:13 ` Xue Fuqiao
2013-06-06 22:15 ` Thien-Thi Nguyen
2013-06-05 17:41 ` Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAF+z6HOwS2BU_LQV_o8+6ct0S1DLj7=in=KG0GO2g4WWGnsxQ@mail.gmail.com' \
--to=xfq.free@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.