From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: RFC - cleaning up /etc
Date: Sun, 12 Jan 2014 01:07:43 +0100 [thread overview]
Message-ID: <m3y52mcbao.fsf@stories.gnus.org> (raw)
In-Reply-To: 20140111205925.GC17111@thyrsus.com
Uhm -- I thought we were in a feature freeze. I.e., we should
concentrate on fixing bugs, and not do lots of non-bug-related changes.
Removing things from etc might be nice, but it doesn't seem to have
anything to do with fixing bugs.
Stefan, please clarify.
As for moving to git, I'm for it, even though git is inferior to bzr in
a few ways (no bound branches, totally icky sha revisions instead of
human-parseable revnos, a `C-x v g' that's so slow it's unusable (but
David is fixing that), worse vc-mode support).
But isn't all this also taking all focus from doing meaningful bug work?
How about waiting until the next feature period opens?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2014-01-12 0:07 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 14:02 RFC - cleaning up /etc Eric S. Raymond
2014-01-09 14:48 ` Samuel El-Borai
2014-01-09 15:09 ` Samuel El-Borai
2014-01-09 16:57 ` Glenn Morris
2014-01-09 17:42 ` Eric S. Raymond
2014-01-09 19:50 ` Glenn Morris
2014-01-10 14:35 ` Richard Stallman
2014-01-10 15:51 ` Eric S. Raymond
2014-01-11 7:15 ` Richard Stallman
2014-01-11 10:17 ` Eric S. Raymond
2014-01-11 18:37 ` Richard Stallman
2014-01-11 10:53 ` Ulrich Mueller
2014-01-11 20:01 ` Glenn Morris
2014-01-11 20:59 ` Eric S. Raymond
2014-01-11 21:10 ` Eli Zaretskii
2014-01-11 21:27 ` Eric S. Raymond
2014-01-12 0:07 ` Lars Magne Ingebrigtsen [this message]
2014-01-12 0:20 ` Eric S. Raymond
2014-01-12 0:37 ` David Kastrup
2014-01-12 3:51 ` Eli Zaretskii
2014-01-25 1:06 ` Progress report on git-blame (was: RFC - cleaning up /etc) David Kastrup
2014-01-25 7:34 ` Eli Zaretskii
2014-01-25 8:59 ` Progress report on git-blame David Kastrup
2014-01-25 9:21 ` martin rudalics
2014-01-25 9:27 ` David Kastrup
2014-01-25 10:12 ` David Kastrup
2014-02-20 18:33 ` David Kastrup
2014-01-25 18:21 ` Lars Ingebrigtsen
2014-01-25 18:30 ` David Kastrup
2014-01-25 18:52 ` Óscar Fuentes
2014-01-25 18:59 ` David Kastrup
2014-01-25 19:31 ` Eli Zaretskii
2014-01-25 19:44 ` Óscar Fuentes
2014-01-25 20:02 ` David Kastrup
2014-01-25 21:45 ` Stefan Monnier
2014-01-26 14:40 ` Aneesh Kumar K.V
2014-01-27 14:17 ` Stefan Monnier
2014-01-25 21:48 ` Stefan Monnier
2014-01-25 23:03 ` Óscar Fuentes
2014-01-26 1:48 ` Stefan Monnier
2014-01-26 17:37 ` Eli Zaretskii
2014-01-26 19:05 ` Stefan Monnier
2014-01-26 19:40 ` Eli Zaretskii
2014-01-26 22:14 ` Stefan Monnier
2014-01-26 6:30 ` David Kastrup
2014-01-26 15:07 ` Stefan Monnier
2014-01-25 8:28 ` David Engster
2014-01-25 9:14 ` David Kastrup
2014-01-12 3:03 ` RFC - cleaning up /etc Stefan Monnier
2014-01-12 13:46 ` Richard Stallman
2014-01-12 19:17 ` 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=m3y52mcbao.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@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 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).