From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: autogen.sh now requires workbook specification
Date: Mon, 01 Apr 2002 11:29:50 -0800 [thread overview]
Message-ID: <E16s7V0-00007Z-00@giblet> (raw)
In-Reply-To: <87g02gdmll.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Sun, 31 Mar 2002 23:17:10 -0600)
From: Rob Browning <rlb@defaultvalue.org>
Date: Sun, 31 Mar 2002 23:17:10 -0600
I had actually thought about that, but didn't know that cvs would be
OK with directories not in the module you checked out inside the
module tree...
i avoid this question by not doing "cvs update" in hack/, but wonder how
cvs would handle that.
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-01 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-31 23:28 autogen.sh now requires workbook specification Thien-Thi Nguyen
2002-04-01 5:00 ` Rob Browning
2002-04-01 5:17 ` Rob Browning
2002-04-01 19:29 ` Thien-Thi Nguyen [this message]
2002-04-01 7:37 ` Thien-Thi Nguyen
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=E16s7V0-00007Z-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-devel@gnu.org \
--cc=ttn@glug.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).