unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: changes in r112843
Date: Wed, 05 Jun 2013 12:46:37 +0200	[thread overview]
Message-ID: <87hahchm2a.fsf@zigzag.favinet> (raw)
In-Reply-To: <CAAF+z6HOwS2BU_LQV_o8+6ct0S1DLj7=in=KG0GO2g4WWGnsxQ@mail.gmail.com> (Xue Fuqiao's message of "Wed, 5 Jun 2013 07:12:24 +0800")

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

() Xue Fuqiao <xfq.free@gmail.com>
() Wed, 5 Jun 2013 07:12:24 +0800

   Remove the (both versions) motivation of branching.

I think most who read this part of the manual will already have
notions of branching as they pertain to their favorite VCS.
Probably what they seek (what we should provide here) is the
assurance that Emacs can be congruent to that particular model,
amongst others.

IOW, in "branch on a tree" the key word in this context is "on".

How about removing motivation and adding in its place text that
qualifies "independent lines" w/ the notion of a (possibly) shared
base (point of intersection) for these lines?  I say "possibly"
because VCS support for multiple roots (full independence) is not
universal, and anyway in practice full independence is almost
entirely undesirable.

-- 
Thien-Thi Nguyen
GPG key: 4C807502

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2013-06-05 10:46 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
2013-06-05 10:46     ` Thien-Thi Nguyen [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hahchm2a.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=xfq.free@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).