From: Eli Zaretskii <eliz@gnu.org>
To: esr@thyrsus.com
Cc: emacs-devel@gnu.org
Subject: Re: Commit practices
Date: Sat, 29 Dec 2007 20:45:04 +0200 [thread overview]
Message-ID: <u1w95xrv3.fsf@gnu.org> (raw)
In-Reply-To: <20071229183244.GA23998@thyrsus.com> (esr@thyrsus.com)
> Date: Sat, 29 Dec 2007 13:32:44 -0500
> From: "Eric S. Raymond" <esr@thyrsus.com>
>
> This brings up the large topic of what to do about our workflow,
> our tools, and the sad fact that Eli's guidelines (while intelligent
> in their way) are basically an attempt to put lipstick on a pig. What
> we should really do is stop kissing the damned pig.
As I wrote in that thread, those aren't _my_ guidelines:
Those are not my rules, I just took a liberty of describing the rules
Richard requested me to follow a long time ago.
So I cannot take the credits for the lipstick.
next prev parent reply other threads:[~2007-12-29 18:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071229141014.3364A2C83DC@grelber.thyrsus.com>
2007-12-29 18:32 ` Commit practices Eric S. Raymond
2007-12-29 18:45 ` Eli Zaretskii [this message]
2007-12-29 20:52 ` Eric S. Raymond
2007-12-30 1:36 ` Richard Stallman
2007-12-30 3:56 ` Stephen J. Turnbull
2007-12-30 6:45 ` Eric S. Raymond
2007-12-30 6:44 ` Eric S. Raymond
2007-12-30 10:08 ` David Kastrup
2007-12-30 10:47 ` Eric S. Raymond
2007-12-30 11:01 ` Miles Bader
2007-12-30 12:36 ` Eric S. Raymond
2007-12-30 12:43 ` Miles Bader
2007-12-30 13:33 ` Eric S. Raymond
2007-12-30 13:51 ` Miles Bader
2007-12-30 14:00 ` David Kastrup
2007-12-30 12:44 ` David Kastrup
2007-12-30 13:39 ` Eric S. Raymond
2007-12-30 13:52 ` David Kastrup
2007-12-30 14:02 ` Richard Stallman
2007-12-30 17:25 ` Eric S. Raymond
2007-12-30 22:58 ` Richard Stallman
2007-12-31 3:25 ` Eric S. Raymond
2007-12-31 22:29 ` Richard Stallman
2007-12-30 7:58 ` Karl Fogel
2007-12-31 0:59 ` Dan Nicolaescu
2007-12-31 22:29 ` Richard Stallman
2008-01-01 0:48 ` Dan Nicolaescu
2008-01-01 22:47 ` Johan Bockgård
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=u1w95xrv3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.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).