From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: doc patch: "Saving Properties" merge into "Format Conversion"
Date: Mon, 07 May 2007 11:38:07 +0200 [thread overview]
Message-ID: <87ps5dotxc.fsf@ambire.localdomain> (raw)
In-Reply-To: <E1HkpAi-0001eF-3m@fencepost.gnu.org> (Richard Stallman's message of "Sun\, 06 May 2007 18\:25\:40 -0400")
() Richard Stallman <rms@gnu.org>
() Sun, 06 May 2007 18:25:40 -0400
When and how to make a release is a question for the maintainer
to decide, and I'm the maintainer.
maintaining the source code requires transparency of source code
manipulation; maintaining the peace requires transparency of intent.
what frustrates people is insufficiency in the latter, not because they
wish to take away the decision from the maintainer, but because they
wish to organize their (parallel, unrelated to the release) efforts
best.
not taking the seething into account is the difference between hardware
and software engineers: in hardware, one-armed-if is a latent bug; even
when you don't care, it's better to explicitly don't care.
practically speaking, i think you would be wise as the maintainer to
declare the trunk open to full-fledged non-release-related hacking, and
confine edits slated only for the release to a branch. (if that branch
is not yet in place, make it immediately, then declare the trunk open.)
that's all i have to say on the matter.
thi
next prev parent reply other threads:[~2007-05-07 9:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 8:15 doc patch: "Saving Properties" merge into "Format Conversion" Thien-Thi Nguyen
2007-05-01 17:25 ` Richard Stallman
2007-05-02 9:28 ` Thien-Thi Nguyen
2007-05-02 17:44 ` Richard Stallman
2007-05-02 19:34 ` Stefan Monnier
2007-05-02 19:50 ` Thien-Thi Nguyen
2007-05-03 2:02 ` Richard Stallman
2007-05-03 2:19 ` Nick Roberts
2007-05-03 8:30 ` Juanma Barranquero
2007-05-03 9:14 ` Kim F. Storm
2007-05-03 23:55 ` Richard Stallman
2007-05-04 1:00 ` Nick Roberts
2007-05-04 7:57 ` Juanma Barranquero
2007-05-04 21:17 ` Richard Stallman
2007-05-04 23:05 ` Kim F. Storm
2007-05-05 23:18 ` Richard Stallman
2007-05-05 0:03 ` Nick Roberts
2007-05-05 23:18 ` Richard Stallman
2007-05-06 0:04 ` David Kastrup
2007-05-06 0:56 ` Nick Roberts
2007-05-06 4:51 ` Miles Bader
2007-05-06 7:37 ` David Kastrup
2007-05-06 11:05 ` Jan Djärv
2007-05-06 11:37 ` David Kastrup
2007-05-06 10:53 ` Juanma Barranquero
2007-05-06 11:17 ` Miles Bader
2007-05-06 11:56 ` Juanma Barranquero
2007-05-06 12:22 ` David Kastrup
2007-05-06 12:51 ` Miles Bader
2007-05-06 14:25 ` Juanma Barranquero
2007-05-06 22:26 ` Richard Stallman
2007-05-07 2:41 ` Stefan Monnier
2007-05-06 16:50 ` Eli Zaretskii
2007-05-06 22:25 ` Richard Stallman
2007-05-07 9:38 ` Thien-Thi Nguyen [this message]
2007-05-04 20:50 ` Kim F. Storm
2007-05-03 9:59 ` Thien-Thi Nguyen
2007-05-03 23:55 ` Richard Stallman
2007-05-04 9:14 ` Thien-Thi Nguyen
2007-05-03 13:55 ` Stefan Monnier
2007-05-07 15:59 ` Kevin Ryde
2007-05-08 20:21 ` Thien-Thi Nguyen
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=87ps5dotxc.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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.