From: Juanma Barranquero <lekktu@gmail.com>
To: Karl Fogel <kfogel@red-bean.com>
Cc: Eric Raymond <esr@thyrsus.com>, Eli Zaretskii <eliz@gnu.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Repo cpnversion progress report
Date: Fri, 31 Jan 2014 18:56:49 +0100 [thread overview]
Message-ID: <CAAeL0SR9CpanDQ25tdP4M92nRrEP3O2vKj_PXZuCVant5Bn=7A@mail.gmail.com> (raw)
In-Reply-To: <87iot0f481.fsf@ktab.red-bean.com>
On Fri, Jan 31, 2014 at 6:31 PM, Karl Fogel <kfogel@red-bean.com> wrote:
> I don't agree with Eli's comments in a later mail about how he wasn't
> sure we should entrust this job to ESR. It's a complex, time-consuming,
> and apparently thankless task; IMHO ESR is doing a good job considering
> all the inputs involved (both human and machine).
Well, do you at least agree with him when he says
> I'm ignored already. You never accepted any argument of mine through
> that long and tiresome "discussion". You are always right and all
> those who disagree with you are always wrong.
and
> I never had any influence over that, because you refuse to listen
> to any dissenting arguments, and prefer to stubbornly do what you
> decided was right ahead of any discussion.
?
Because that's also my feeling about every single switching-to-git
discussion we've had so far. The only thing Eric has backtracked about
is the imminence of switching, and that because Stefan specifically
said that it wouldn't happen during the freeze.
J
next prev parent reply other threads:[~2014-01-31 17:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 19:55 Repo cpnversion progress report Eric S. Raymond
2014-01-30 20:11 ` Andreas Schwab
2014-01-30 20:27 ` Eric S. Raymond
2014-01-30 22:04 ` Andreas Schwab
2014-01-30 21:23 ` Eli Zaretskii
2014-01-30 21:42 ` Eric S. Raymond
2014-01-31 7:50 ` Eli Zaretskii
2014-01-31 15:25 ` Eric S. Raymond
2014-01-31 15:57 ` David Kastrup
2014-01-31 16:15 ` Eli Zaretskii
2014-01-31 17:31 ` Karl Fogel
2014-01-31 17:56 ` Juanma Barranquero [this message]
2014-01-31 19:23 ` Eric S. Raymond
2014-01-31 19:55 ` Juanma Barranquero
2014-01-31 20:30 ` Eli Zaretskii
2014-01-31 21:20 ` Sean Sieger
2014-01-31 21:22 ` Sean Sieger
2014-02-01 9:38 ` David Kastrup
2014-01-31 19:31 ` Karl Fogel
2014-01-31 20:18 ` Eli Zaretskii
2014-02-01 11:04 ` Richard Stallman
2014-01-31 18:16 ` Eric S. Raymond
2014-01-31 19:44 ` Paul Eggert
2014-01-31 21:07 ` Eric S. Raymond
2014-02-01 0:05 ` Paul Eggert
2014-02-01 0:25 ` Juanma Barranquero
2014-02-01 4:19 ` Eric S. Raymond
2014-02-01 8:40 ` Eli Zaretskii
2014-02-02 1:03 ` Stefan Monnier
2014-01-31 21:03 ` Stefan Monnier
2014-01-31 21:51 ` Eric S. Raymond
2014-01-31 23:15 ` Jan D.
2014-02-01 4:22 ` Eric S. Raymond
2014-01-31 23:16 ` Stefan Monnier
2014-02-01 4:26 ` Eric S. Raymond
2014-02-01 11:04 ` Eli Zaretskii
2014-02-02 0:58 ` Stefan Monnier
2014-02-02 10:24 ` Eric S. Raymond
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='CAAeL0SR9CpanDQ25tdP4M92nRrEP3O2vKj_PXZuCVant5Bn=7A@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
--cc=kfogel@red-bean.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).