From: Karl Fogel <kfogel@red-bean.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [beuc@gnu.org: Re: [Savannah-hackers-public] bzr move from sftp:// to bzr+ssh:// [done]]
Date: Sun, 10 Oct 2010 13:07:15 -0400 [thread overview]
Message-ID: <87eibyc6yk.fsf@red-bean.com> (raw)
In-Reply-To: <87sk0examu.fsf@lola.goethe.zz> (David Kastrup's message of "Sun, 10 Oct 2010 18:42:17 +0200")
David Kastrup <dak@gnu.org> writes:
>Eli Zaretskii <eliz@gnu.org> writes:
>> Reportedly, there were some untold difficulties to do so. Given the
>> number of minutes it took today, I have my doubts.
Hardly "untold"; see below.
>The great Chinese emperor commissioned a painting of a rooster from a
>famous artist. The artist told him that it would take considerable
>time. After months and months of reminders and delays, the emperor went
>to artist in person and entered his house, telling him that he would
>stay at his place until the painting was done. The artist put an empty
>canvas on the scaffold [ok, somebody better versed in Chinese art please
>substitute the correct materials here], took his brush and ink, and with
>few swift and determined strokes put the perfect likeness of a rooster
>to the canvas, scarcely taking a minute.
>
>The emperor was furious: "You let me wait that long for a painting
>taking a minute? What for?". Without a word, the artist opened the
>door to his work room: the room was plastered, wall and ceiling, with
>different paintings of roosters, stacks of them piling up on the floor.
As one of the rooster painters, I can say it was not just a matter of
minutes for someone unfamiliar with the GNU systems and trying to do it
in a maintainable way :-). Perhaps it was that easy for Sylvain; in any
case I'm glad he was able to get to it.
In public posts, I detailed some of this. Elsethread from the below,
you can see some of the problems I ran into, how long it could sometimes
take to get questions answered, etc. This is *not* to blame the GNU
sysadmins: they are volunteers, they work hard, and there is always too
much to do. It's just not an easy system for integrating new volunteers
or drive-by contributions, unfortunately.
http://lists.gnu.org/archive/html/savannah-hackers-public/2010-05/msg00024.html
http://lists.gnu.org/archive/html/savannah-hackers-public/2010-06/msg00015.html
http://lists.gnu.org/archive/html/savannah-hackers-public/2010-05/threads.html#00001
When I finally decided I didn't have time to deal with it, I also posted
publicly saying that I was off the job, and referencing the above posts
both to explain why and to show the status to whoever might pick it up.
All credit to Sylvain for getting it done.
-Karl
next prev parent reply other threads:[~2010-10-10 17:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 12:39 [beuc@gnu.org: Re: [Savannah-hackers-public] bzr move from sftp:// to bzr+ssh:// [done]] Eli Zaretskii
2010-10-10 12:56 ` Lars Magne Ingebrigtsen
2010-10-10 13:47 ` Andreas Schwab
2010-10-10 13:49 ` Eli Zaretskii
2010-10-10 14:01 ` Lars Magne Ingebrigtsen
2010-10-10 14:30 ` Eli Zaretskii
2010-10-10 16:42 ` David Kastrup
2010-10-10 17:07 ` Karl Fogel [this message]
2010-10-11 4:55 ` Richard Stallman
2010-10-10 12:57 ` Andreas Schwab
2010-10-10 14:03 ` B Smith-Mannschott
2010-10-10 14:36 ` Eli Zaretskii
2010-10-10 14:56 ` Eli Zaretskii
2010-10-10 16:07 ` Andreas Schwab
2010-10-10 17:01 ` Christoph
2010-10-11 7:01 ` Sven Joachim
2010-10-11 11:54 ` Lennart Borgman
2010-10-11 13:05 ` Andreas Schwab
2010-10-11 14:06 ` Lennart Borgman
2010-10-11 15:33 ` Jason Earl
2010-10-11 19:05 ` Eli Zaretskii
2010-10-11 20:26 ` Karl Fogel
2010-10-11 20:44 ` Eli Zaretskii
2010-10-11 22:18 ` Jason Earl
2010-10-12 3:21 ` Stephen J. Turnbull
2010-10-11 15:46 ` Óscar Fuentes
2010-10-13 0:27 ` Stefan Monnier
2010-10-14 0:42 ` Christoph
-- strict thread matches above, loose matches on Subject: below --
2010-10-10 13:03 Richard Stallman
2010-10-18 21:07 ` Alan Mackenzie
2010-10-19 4:00 ` Eli Zaretskii
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=87eibyc6yk.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=dak@gnu.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 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.