From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Theodore Tso <tytso@mit.edu>
Cc: David Kastrup <dak@gnu.org>, Jeff King <peff@peff.net>,
git@vger.kernel.org
Subject: Re: Terminology question about remote branches.
Date: Sun, 05 Aug 2007 09:27:38 -0700 [thread overview]
Message-ID: <86lkcqvtdx.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20070805154801.GD28263@thunk.org> (Theodore Tso's message of "Sun, 5 Aug 2007 11:48:01 -0400")
>>>>> "Theodore" == Theodore Tso <tytso@mit.edu> writes:
Theodore> To use a GNU emacs example, consider M-x customize, which is this
Theodore> huge, very fancy, *very* complex hierarchical mechanism with a
Theodore> pointy-clicky interface for setting options. Most emacs experts
Theodore> wouldn't use it, preferring to open code raw emacs-lisp settings in
Theodore> their .emacs.el. If you ask an old-time emacs user how to set up
Theodore> some specific feature setting via M-x customize, they might look at
Theodore> you blankly, because it's not an interface they use much, if at all.
I beg to differ. I *am* an old-time Emacs user, and I resisted customize when
it first appeared, because *most* of the things still didn't use it. However,
as of a year ago, I assessed that customize had gotten to "critical mass", and
that 75% of my .emacs could be replaced by it. So I have, and it's made
things simpler for me.
So, it just has to be complete enough and flexible enough.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2007-08-05 16:27 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 10:55 Terminology question about remote branches David Kastrup
2007-08-04 12:02 ` Jeff King
2007-08-04 12:36 ` David Kastrup
2007-08-04 13:07 ` Lars Hjemli
2007-08-04 13:38 ` David Kastrup
2007-08-04 14:03 ` Lars Hjemli
2007-08-04 14:11 ` David Kastrup
2007-08-04 14:25 ` David Kastrup
2007-08-04 14:35 ` Lars Hjemli
2007-08-04 15:09 ` David Kastrup
2007-08-04 15:48 ` Lars Hjemli
2007-08-05 9:24 ` Jeff King
2007-08-04 14:50 ` Julian Phillips
2007-08-04 17:00 ` David Kastrup
2007-08-04 17:19 ` Julian Phillips
2007-08-04 18:00 ` David Kastrup
2007-08-04 22:56 ` Theodore Tso
2007-08-05 7:06 ` David Kastrup
2007-08-05 9:21 ` Jeff King
2007-08-05 9:29 ` David Kastrup
2007-08-05 9:32 ` Jeff King
2007-08-05 9:44 ` David Kastrup
2007-08-05 9:46 ` Jeff King
2007-08-04 12:14 ` Jakub Narebski
2007-08-04 13:29 ` Sean
2007-08-04 14:01 ` David Kastrup
2007-08-04 14:48 ` Sean
2007-08-04 15:22 ` David Kastrup
2007-08-05 10:10 ` Jeff King
2007-08-05 10:05 ` Jeff King
2007-08-05 10:56 ` Steffen Prohaska
2007-08-05 11:02 ` Jeff King
2007-08-05 11:38 ` David Kastrup
2007-08-05 11:52 ` Jeff King
2007-08-05 12:12 ` David Kastrup
2007-08-05 12:14 ` Jeff King
2007-08-05 15:48 ` Theodore Tso
2007-08-05 16:23 ` David Kastrup
2007-08-05 16:27 ` Randal L. Schwartz [this message]
2007-08-05 16:40 ` Sean
2007-08-05 16:45 ` Jeff King
2007-08-05 7:31 ` Junio C Hamano
2007-08-05 10:07 ` Steffen Prohaska
2007-08-05 14:23 ` Julian Phillips
2007-08-05 15:09 ` David Kastrup
2007-08-05 15:24 ` Julian Phillips
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=86lkcqvtdx.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=tytso@mit.edu \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox