From: Rhys Ulerich <rhys.ulerich@gmail.com>
To: gsl-discuss@sourceware.org
Subject: Re: Copy in autogen.sh?
Date: Tue, 05 Nov 2013 16:29:00 -0000 [thread overview]
Message-ID: <CAKDqugS8J_CRO4u9v_PMGh7OXAppfOxs4ARdM40Ez9JtWkhypg@mail.gmail.com> (raw)
In-Reply-To: <CAKDqugT0OFZ1AFrC3Gnz4X06RvCiLPde=gOw87Q=3yHGG5mySw@mail.gmail.com>
> I'm inclined to add --copy to the automake invocation so the behavior
> is consistent.
The --copy option, if that's consensus, process would also require
tweaking libtoolize. I'd take a pass through those separate
invocations in autogen.sh to make sure things are consistent across
all of them.
- Rhys
prev parent reply other threads:[~2013-11-05 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 16:16 Rhys Ulerich
2013-11-05 16:29 ` Rhys Ulerich [this message]
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=CAKDqugS8J_CRO4u9v_PMGh7OXAppfOxs4ARdM40Ez9JtWkhypg@mail.gmail.com \
--to=rhys.ulerich@gmail.com \
--cc=gsl-discuss@sourceware.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).