From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Charles Wilson <cwilson@ece.gatech.edu>
Cc: Robert Collins <robert.collins@itdomain.com.au>,
"Gerrit P. Haase" <cygwin@cygwin.com>
Subject: Re: experimental texmf packages
Date: Thu, 06 Dec 2001 00:30:00 -0000 [thread overview]
Message-ID: <m3g06o3gia.fsf@appel.lilypond.org> (raw)
In-Reply-To: <3C0E5FE5.9040908@ece.gatech.edu> (Charles Wilson's message of "Wed, 05 Dec 2001 12:56:53 -0500")
Charles Wilson <cwilson@ece.gatech.edu> writes:
> > different naming convention, ie foo-1.1-cyg.tar.gz?
>
> probably too late -- non-maintainers who want to build it personally
> should just download and follow the instructions.
Hmm, that sounds awfully unscriptable :-) Am I the only non-maintainer
that uses a script?
Now for something constructive. What if I fix my scripts to do the
new convention, and we run that over the archive to rebuild everything?
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-12-06 8:22 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 7:57 Jan Nieuwenhuizen
2001-11-18 20:43 ` Gerrit P. Haase
2001-11-19 6:34 ` Jerome BENOIT
2001-11-28 13:47 ` Jerome BENOIT
2001-11-19 8:33 ` Charles Wilson
2001-11-28 14:44 ` Charles Wilson
2001-11-19 11:51 ` Charles Wilson
2001-11-19 12:09 ` Gerrit P. Haase
2001-11-28 23:31 ` Gerrit P. Haase
2001-11-28 20:42 ` Charles Wilson
2001-11-20 3:00 ` Jan Nieuwenhuizen
2001-11-20 6:28 ` Gerrit P. Haase
2001-11-20 6:51 ` Charles Wilson
2001-11-29 13:56 ` Charles Wilson
2001-11-29 13:36 ` Gerrit P. Haase
2001-12-03 0:56 ` Jan Nieuwenhuizen
2001-12-03 5:26 ` Gerrit P. Haase
2001-12-03 6:07 ` Jan Nieuwenhuizen
2001-12-04 19:32 ` Charles Wilson
2001-12-05 4:35 ` Jan Nieuwenhuizen
2001-12-05 5:53 ` Robert Collins
2001-12-05 6:19 ` Jan Nieuwenhuizen
2001-12-05 10:21 ` Charles Wilson
2001-12-06 0:30 ` Jan Nieuwenhuizen [this message]
2001-12-06 8:24 ` Charles Wilson
2001-12-06 8:31 ` Jan Nieuwenhuizen
2001-12-05 15:49 ` Charles Wilson
2001-12-06 1:18 ` Jan Nieuwenhuizen
2001-12-05 15:35 ` Charles Wilson
2001-12-06 1:08 ` Jan Nieuwenhuizen
2001-12-06 7:49 ` Christopher Faylor
2001-12-06 8:18 ` Charles Wilson
2001-12-07 18:39 ` Robert Collins
2001-12-07 18:48 ` Charles Wilson
2001-12-07 18:59 ` Robert Collins
2001-12-08 5:58 ` Gerrit P. Haase
2001-12-08 8:51 ` lists, reply-to (was: experimental texmf packages) Jochen Küpper
2001-12-08 14:31 ` Robert Collins
2001-12-08 16:26 ` Robert Collins
2002-01-30 2:32 ` guile-1.6 [WAS: experimental texmf packages] Jan Nieuwenhuizen
2001-11-20 6:38 ` experimental texmf packages Jerome BENOIT
2001-11-20 11:34 ` Gerrit P. Haase
2001-11-20 18:02 ` Jerome BENOIT
2001-11-30 9:29 ` Jerome BENOIT
2001-11-30 0:07 ` Gerrit P. Haase
2001-11-20 17:54 ` Jan Nieuwenhuizen
2001-11-30 9:09 ` Jan Nieuwenhuizen
2001-11-29 13:43 ` Jerome BENOIT
2001-11-29 7:46 ` Jan Nieuwenhuizen
2001-11-28 8:41 ` Gerrit P. Haase
2001-11-23 5:24 ` Jan Nieuwenhuizen
2001-12-05 22:47 Billinghurst, David (CRTS)
2001-12-08 13:28 ` Jan Nieuwenhuizen
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=m3g06o3gia.fsf@appel.lilypond.org \
--to=janneke@gnu.org \
--cc=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.com \
--cc=robert.collins@itdomain.com.au \
/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).