From: Steve Ellcey <sje@cup.hp.com>
To: drow@false.org, keiths@redhat.com
Cc: bje@au1.ibm.com, insight@sourceware.org, binutils@sourceware.org,
gdb@sourceware.org, sid@sourceware.org
Subject: Re: Update configure in tk/tcl/itcl
Date: Wed, 12 Jul 2006 16:50:00 -0000 [thread overview]
Message-ID: <200607121650.JAA05638@hpsje.cup.hp.com> (raw)
In-Reply-To: <20060712162704.GA22834@nevyn.them.org>
> > The last three src subdirectories that still use the old autoconf 2.19
> > are tk, tcl, and itcl. This patch is to update the autoconf used by
> > those subdirectories.
> > Ok for checkin?
>
> Steve, did you ever get any response from this patch? I don't want to
> let the autoconf upgrade get stalled. I think it's reasonable to go
> ahead and commit this if none of the Insight maintainers explicitly
> object.
>
> --
> Daniel Jacobowitz
> CodeSourcery
I got a reply from Keith Seitz asking if I had write permssion to the
repository of if I wanted him to commit the patches. I told him I did
have write permission but that I was heading off to the GCC Summit and
did not want to do the checkin and then go off line for several days.
Keith, have you done anything with the patches? Should I check them in
now that I am back?
I also got a reply from Ben Elliston letting me know that sid depends on
Tcl because it has a tcl bridge. This was in reply to my claim that
insight was now the only tcl user in the src tree.
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2006-07-12 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 17:59 Steve Ellcey
2006-07-12 16:27 ` Daniel Jacobowitz
2006-07-12 16:50 ` Steve Ellcey [this message]
2006-07-12 17:21 ` Keith Seitz
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=200607121650.JAA05638@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=binutils@sourceware.org \
--cc=bje@au1.ibm.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=insight@sourceware.org \
--cc=keiths@redhat.com \
--cc=sid@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).