From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com, kewarken@qnx.com
Subject: Re: [Patch] correctly configure wcwidth in readline
Date: Wed, 26 Feb 2003 16:57:00 -0000 [thread overview]
Message-ID: <200302261657.h1QGv1Q27270@duracef.shout.net> (raw)
Hi Kris,
> What is the procedure for regenerating configure scripts?
> Should I regenerate it here and commit it or do you have a certain person
> who does it under a specific environment?
I just finished my first configure patch so I just went through this.
You should build autoconf 2.13 from ftp.gnu.org and use that to regenerate
'configure'. Diff 'configure' afterwards to make sure that the only
differences are the changes you made + a couple of thousand lines of
silly line-number differences.
Don't include the configure diffs in your patch message, but do check
them into CVS when you commit.
As far as the patch goes, it's up to Elena Z to say what to do.
I'll volunteer to help out if she would like.
Michael C
next reply other threads:[~2003-02-26 16:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 16:57 Michael Elizabeth Chastain [this message]
2003-02-26 18:23 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 20:14 Michael Elizabeth Chastain
2003-02-26 17:35 Kris Warkentin
2003-02-26 18:06 ` Daniel Jacobowitz
2003-02-26 17:44 ` Kris Warkentin
2003-02-26 17:51 ` Daniel Jacobowitz
[not found] ` <00fd01c2ddc0$28ab75e0$0202040a@catdog>
[not found] ` <20030226175915.GA15700@nevyn.them.org>
2003-02-26 18:43 ` Kris Warkentin
2003-02-26 20:14 ` Daniel Jacobowitz
2003-02-26 20:40 ` Kris Warkentin
2003-02-26 20:49 ` Daniel Jacobowitz
2003-02-26 20:52 ` Kris Warkentin
2003-03-03 2:55 ` Elena Zannoni
2003-03-03 14:46 ` Kris Warkentin
2003-02-26 21:26 ` Andreas Schwab
2003-02-26 16:47 Kris Warkentin
2003-02-26 16:54 ` Daniel Jacobowitz
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=200302261657.h1QGv1Q27270@duracef.shout.net \
--to=mec@shout.net \
--cc=gdb-patches@sources.redhat.com \
--cc=kewarken@qnx.com \
/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