unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Andreas Schwab'" <schwab@linux-m68k.org>
Cc: 'Eli Zaretskii' <eliz@gnu.org>, emacs-devel@gnu.org
Subject: RE: dev-tsdh-* themes
Date: Sat, 8 Jan 2011 09:33:21 -0800	[thread overview]
Message-ID: <34CB0B2DD28D483C9B6628779CC27618@us.oracle.com> (raw)
In-Reply-To: <m2oc7r9y0o.fsf@igel.home>

> > So did Emacs itself have a `contrib' subdir, decades ago
           ^^^^^

> $ git log --name-only --format=%% | grep contrib/
> [nothing]

I specifically said that it might have been another Emacs from GNU Emacs.  Emacs
is not (heresy!) synonymous with GNU Emacs.  Emacs has a longer (yes) and richer
(yes) history than what you will find by grepping GNU Emacs logs.

(But thanks to you and `grep' for showing that GNU Emacs has no record of a
`contrib' subdir.)

My point was that it is not only "these days" that a `contrib' subdir is used
"for files contributed by people other than the immediate maintainers".  That
practice is nothing new.  It has a very long history, including within Emacs.




  reply	other threads:[~2011-01-08 17:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07  9:46 dev-tsdh-* themes Eli Zaretskii
2011-01-07 10:35 ` Tassilo Horn
2011-01-07 10:51   ` Eli Zaretskii
2011-01-08  2:48     ` Glenn Morris
2011-01-08  2:50       ` Glenn Morris
2011-01-08  9:25         ` Chad Brown
2011-01-08  9:44           ` Eli Zaretskii
2011-01-08 12:33           ` Dimitri Fontaine
2011-01-08  9:38         ` Eli Zaretskii
2011-01-08 10:10           ` Philipp Haselwarter
2011-01-08 12:05             ` Eli Zaretskii
2011-01-08 15:37           ` Drew Adams
2011-01-08 16:10             ` Andreas Schwab
2011-01-08 17:33               ` Drew Adams [this message]
2011-01-08 17:53       ` Chong Yidong
2011-01-08 18:10         ` Glenn Morris
2011-01-08 17:59   ` Chong Yidong

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=34CB0B2DD28D483C9B6628779CC27618@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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).