From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: robertl@dgii.com, wilson@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: toplev.h, revision.next
Date: Wed, 06 May 1998 14:01:00 -0000 [thread overview]
Message-ID: <199805062101.RAA13991@caip.rutgers.edu> (raw)
> From: Robert Lipe <robertl@dgii.com>
> Subject: Re: toplev.h, revision.next
>
> > This looks OK to me.
>
> It's now committed
>
> > Please tell me the Makefile dependency lists are machine generated...
> >
> > No, they aren't. Kaveh has just been hand adding system.h to dependency
> > lists everytime he adds an include. Ideally we should do the same thing
>
> Sounds like a good job for a computer.
No need to fear, automake is here! :-)
Is anyone interested in taking on this challenge?
--
Kaveh R. Ghazi Project Manager / Custom Development
ghazi@caip.rutgers.edu Icon CMT Corp.
next reply other threads:[~1998-05-06 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-06 14:01 Kaveh R. Ghazi [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-05-03 23:47 Robert Lipe
1998-05-05 23:29 ` Jim Wilson
1998-05-06 11:36 ` Robert Lipe
1998-05-06 16:13 ` Jim Wilson
1998-05-06 17:12 ` Jim Wilson
1998-05-06 23:49 ` Robert Lipe
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=199805062101.RAA13991@caip.rutgers.edu \
--to=ghazi@caip.rutgers.edu \
--cc=egcs@cygnus.com \
--cc=robertl@dgii.com \
--cc=wilson@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).