From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: Rob Browning <rlb@defaultvalue.org>, guile-devel@gnu.org
Subject: Re: Can't "make dist" for 1.5.7.
Date: 23 Jul 2002 23:33:09 +0200 [thread overview]
Message-ID: <87bs8yku3u.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3fzyaxi3p.fsf@laruns.ossau.uklinux.net>
Neil Jerram <neil@ossau.uklinux.net> writes:
> Rob> Actually make dist is not just generating a new file, but
> Rob> also running a cvs checkout/checkin for it. Do we actually
> Rob> want that? I tend to think that "make dist" should take a
> Rob> fixed set of files (at least CVS-wise) and produce a
> Rob> tarfile.
>
> I agree.
Me too. People that don't use our CVS repo should also be painlessly
able to "make dist" etc.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-23 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 22:38 Can't "make dist" for 1.5.7 Rob Browning
2002-07-22 22:28 ` Rob Browning
2002-07-23 21:14 ` Neil Jerram
2002-07-23 21:33 ` Marius Vollmer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-25 13:50 stefan
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bs8yku3u.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.org \
--cc=rlb@defaultvalue.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).