From: gamename <namesagame-usenet@yahoo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: CVS Repos For Lisp Code
Date: Sun, 13 Jan 2008 11:48:48 -0800 (PST) [thread overview]
Message-ID: <edb51ea0-5c87-4def-9d80-fa62354dd690@i3g2000hsf.googlegroups.com> (raw)
In-Reply-To: 86abn9czbt.fsf@timbral.net
On Jan 13, 11:14 am, Evans Winner <tho...@timbral.net> wrote:
> gamename <namesagame-use...@yahoo.com> writes:
>
> We were thinking of trying to expand the sourceforge project to
> automatically include source files from gnu-emacs-sources (see
> http://www.emacswiki.org/cgi-bin/wiki/WikifiedEmacsLispList).
>
> Is this stuff scraped from the archives by hand, or is it done by
> script? There has been far more code posted to g.e.s over the years
> than just what's here, hasn't there?
True. We will probably end up looking in many more places than g-e-s.
>
> Anyway, it sounds like a good idea. I mean, can it hurt?
I can't see how it would.
next prev parent reply other threads:[~2008-01-13 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 19:08 CVS Repos For Lisp Code gamename
2008-01-13 19:14 ` Evans Winner
2008-01-13 19:48 ` gamename [this message]
2008-01-14 5:16 ` Mike Mattie
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=edb51ea0-5c87-4def-9d80-fa62354dd690@i3g2000hsf.googlegroups.com \
--to=namesagame-usenet@yahoo.com \
--cc=help-gnu-emacs@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.
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).