unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fren Zeee <frenzeee@gmail.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, "Chad Brown" <yandros@mit.edu>,
	emacs-devel@gnu.org
Subject: Re: What is emacs architecture ?
Date: Mon, 19 Jul 2010 23:21:09 -0700	[thread overview]
Message-ID: <AANLkTinXL8YQr-DtVXBJhpyFoACDlQ8sI0rmcTBtklN3@mail.gmail.com> (raw)
In-Reply-To: <87iq4azyvs.fsf@uwakimon.sk.tsukuba.ac.jp>

On Mon, Jul 19, 2010 at 7:10 PM, Stephen J. Turnbull <stephen@xemacs.org> wrote:
> Chad Brown writes:
>
>  > For finding a `consistent set', you're really going to want to read
>  > up on Bazaar first.  The concepts that you want here are `tags' and
>  > perhaps `branches', but I recommend that you read the overview
>  > first.
>
> Not really.  In CVS you need tags for consistency, but in Emacs
> practice in a modern VCS, pretty much every version accessible via the
> VCS is going to be "consistent" in the sense of "intended to be
> built".  Specifically, in Bazaar commits are formally synchronous
> across the whole repository (aka atomic), and Emacs practice means
> that will usually mean semantically synchronous (consistent) as well.
>
> Of course, the OP also required "released", so that narrows the field
> to tags (probably not branches).
>
> Aside: This consistency is likely to change in certain ways in the
> future, since I don't see a lot of appetite among Emacs developers for
> Linux-kernel-style rebasing before pushing, but feature branches are
> way too useful to be avoided.  So I expect that the mainline (as
> defined by bzr) will appear as a sequence of usually consistent (ie,
> buildable) revisions, with standalone commits mixed with merges.
> However, revisions on branches merged by many developers will probably
> be much less reliable, unless an explicit policy of only clean commits
> in the public repo is adopted.
>
>

This newbie thanks for your past help and looks for more till able to
contribute.

If the experts are in slight disagreement as above, let me explain
what I want to do. First, I plan to read on Bazaar in some days and
prepare a debian/ubuntu with bazaar to download the repository. I
certainly want to isolate from this big collection of the subset
directory structure of the earliest and simplest and minimal emacs. I
am not interested at this stage in any latest emacs. I want some
_qualified_ suggestions on which would be the most instructive release
to play with. This exercise at this stage is for purely educational
purpose - as we appreciate the value of pure maths, pure science and
pure research. Contributions in this way comes later with strong
inspiration. People's minds work differently.

To facilitate refererral to various versions of emacs (in the absence
of bazaar working as yet on my system) here is a chart I have. I am
wondering what kind of gui chart will bazaar show to me.

From: http://www.jwz.org/doc/emacs-timeline.html

1985  GNU Emacs 13.0? (20-mar-85)
      by Richard Stallman.
      initial public release?
             |
      GNU Emacs 15.10 (11-apr-85)
             |
      GNU Emacs 15.34 (07-may-85)
             |
      GNU Emacs 16.56 (15-jul-85)
      (Gosling code expunged
      for copyright reasons)
             |
             |
      GNU Emacs 16.60 (19-sep-85)
      (contained first patches from
      the net, including preliminary
      SYSV support)



  parent reply	other threads:[~2010-07-20  6:21 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07  5:50 What is emacs architecture ? Fren Zeee
2010-07-07  6:07 ` Masatake YAMATO
2010-07-07 15:26   ` Karl Fogel
2010-07-07 15:36     ` Drew Adams
2010-07-07 17:30       ` Stephen Berman
2010-07-07 20:02         ` Karl Fogel
2010-07-07 22:28           ` Fren Zeee
2010-07-07 22:32             ` Karl Fogel
2010-07-08  3:27             ` Stephen J. Turnbull
2010-07-08  4:16               ` Jeff Clough
2010-07-19  4:49                 ` Fren Zeee
2010-07-08  7:06             ` Eli Zaretskii
2010-07-08  7:40             ` Thien-Thi Nguyen
2010-07-08 17:37               ` Karl Fogel
2010-07-19  4:35                 ` Fren Zeee
2010-07-19 14:43                   ` Óscar Fuentes
2010-07-19 17:12                     ` Chad Brown
2010-07-19 22:04                       ` Fren Zeee
2010-07-19 22:39                         ` Chad Brown
2010-07-20  2:10                           ` Stephen J. Turnbull
2010-07-20  2:58                             ` Óscar Fuentes
2010-07-20  5:19                               ` Stephen J. Turnbull
2010-07-20 12:53                                 ` Óscar Fuentes
2010-07-20  3:00                             ` Miles Bader
2010-07-20  3:24                               ` Óscar Fuentes
2010-07-20  5:13                                 ` Miles Bader
2010-07-20 12:42                                   ` Óscar Fuentes
2010-07-20  5:21                               ` Stephen J. Turnbull
2010-07-20  6:21                             ` Fren Zeee [this message]
2010-07-20  8:23                               ` Stephen J. Turnbull
2010-07-20  8:59                                 ` Andreas Schwab
2010-07-21  3:25                                   ` Fren Zeee
2010-07-21  7:51                                     ` Andreas Schwab
2010-07-21  3:28                                 ` Fren Zeee
2010-07-21 14:49                                   ` David Robinow
2010-07-20  8:48                               ` Andreas Schwab
2010-07-07 18:15   ` Fren Zeee
2010-07-08  0:09     ` Stephen J. Turnbull
2010-07-08  6:42       ` Eli Zaretskii
2010-07-08  8:22         ` Stephen J. Turnbull
2010-07-08  9:44           ` Eli Zaretskii
2010-07-07 18:51   ` Fren Zeee

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=AANLkTinXL8YQr-DtVXBJhpyFoACDlQ8sI0rmcTBtklN3@mail.gmail.com \
    --to=frenzeee@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    --cc=stephen@xemacs.org \
    --cc=yandros@mit.edu \
    /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).