| To: | kenmcd@xxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: configure.in |
| From: | Alan Hoyt <ahoyt@xxxxxxxxxxxxx> |
| Date: | Fri, 20 Jun 2003 09:57:17 -0500 |
| Cc: | pcp@xxxxxxxxxxx, Mark Goodwin <markgw@xxxxxxxxxxxxxxxxx> |
| In-reply-to: | <Pine.LNX.4.44.0306200924051.4945-100000@kenj-pc.melbourne.sgi.com> |
| References: | <Pine.LNX.4.44.0306200924051.4945-100000@kenj-pc.melbourne.sgi.com> |
| Sender: | pcp-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 |
kenmcd@xxxxxxxxxxxxxxxxx wrote: BUT, the -017 build there is bad (we suspect) ... concurrent investigations are proceeding ... we'll post to the list when the coast is clear again, and the new tarball in the dev directory will certainly contain the configure.in fix. Three questions: Can you start using build numbers in your tarball naming convention (i.e. like your rpms)? Can you also release dev snapshots in tarball format? Can you push out dev snapshot’s more frequently – you’ve jumped from -14 to -17 which is now really 2.4?
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: configure.in, kenmcd |
|---|---|
| Next by Date: | Re: configure.in, kenmcd |
| Previous by Thread: | Re: configure.in, kenmcd |
| Next by Thread: | Re: configure.in, kenmcd |
| Indexes: | [Date] [Thread] [Top] [All Lists] |