From: Joshua N Pritikin <jpritikin@pobox.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Document git-runstatus
Date: Mon, 20 Nov 2006 12:45:29 +0530 [thread overview]
Message-ID: <20061120071529.GF3315@always.joy.eth.net> (raw)
In-Reply-To: <20061119181307.GY7201@pasky.or.cz>
On Sun, Nov 19, 2006 at 07:13:08PM +0100, Petr Baudis wrote:
> BTW, I've finally found a fine example of situation parallel to Git:
> TeX! There are the core TeX commands (plumbing) and plain TeX (basic
> porcelain) on top of that as well as a bunch of other macro sets (other
> porcelains). Now I need to dig out The TeXbook from wherever I've put it
> to see how did Knuth deal with it, documentation-wise.
Gahh! Please don't use TeX as an example. As far as I know, TeX doesn't
offer lexical scope. Hence, action-at-a-distance is commonplace which
makes program execution extremely difficult for mere mortals to
predict. I am constantly amazed at popularity of TeX, in spite of its
grave deficiencies. Perhaps there isn't a good alternative yet.
next prev parent reply other threads:[~2006-11-20 7:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 14:15 [PATCH] Document git-runstatus Rene Scharfe
2006-11-18 14:26 ` Sean
[not found] ` <20061118092644.a9f15669.seanlkml@sympatico.ca>
2006-11-18 14:35 ` Petr Baudis
2006-11-18 15:04 ` Rene Scharfe
2006-11-18 16:04 ` Sean
2006-11-18 18:20 ` A Large Angry SCM
2006-11-18 18:49 ` Sean
[not found] ` <455F60EA.2080009@gmail.com>
2006-11-18 20:04 ` Sean
[not found] ` <20061118150431.81076072.seanlkml@sympatico.ca>
2006-11-19 18:13 ` Petr Baudis
2006-11-20 7:15 ` Joshua N Pritikin [this message]
2006-11-20 8:11 ` Jakub Narebski
2006-11-18 18:49 ` Junio C Hamano
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=20061120071529.GF3315@always.joy.eth.net \
--to=jpritikin@pobox.com \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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 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.