From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: spu autoconfiscation patch
Date: Tue, 02 Apr 2002 12:04:00 -0000 [thread overview]
Message-ID: <20020402150500.B8031@nevyn.them.org> (raw)
In-Reply-To: <20020402195614.GA10282@doctormoo.dyndns.org>
On Tue, Apr 02, 2002 at 02:56:14PM -0500, Nathanael Nerode wrote:
> Reposting...
>
> 'configure' is not included in the patch below because I couldn't get
> cvs diff to handle a new file. It's generated from configure.in anyway.
>
> The whole files are probably easier to read than the diffs.
Please don't use straight diff; it's unreadable. Use contextual or
unified diffs - I think the preference for most GNU projects is
contextual (I'm a unified person, myself....)
> I did not attempt to cure any bugs or portability issues in SPU, as I
> do not feel that I am a competent enough C programmer to do so; this is
> just enough that the 'utils' and top level autoconfiscations will be
> possible.
>
> With this patch, spu configures, builds, and has no behavior changes on
> my Debian woody system (i686-pc-linux-gnu). (The programs which SPU
> generates are identical before and after.)
>
> Apr 2 2002 Nathanael Nerode
You also may want to look at GNU changelog formatting. That should be:
2002-04-02 Nathanael Nerode <neroden@doctormoo.dyndns.org>
(note the double spaces)
> * utils/spu/configure.in: autoconfiscated.
> * utils/spu/Makefile.in: autoconfiscated.
> * utils/spu/configure: new autoconf-generated file.
GDB folks: This patch is simple and seems obviously correct to me.
Since I'm allowed to check in changes to configury, I'm going to sit on
this for two or three days, and check it in to the trunk if there are
no objections. Speak now or, etc.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-04-02 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 11:56 Nathanael Nerode
2002-04-02 12:02 ` Stan Shebs
2002-04-02 12:06 ` Daniel Jacobowitz
2002-04-02 12:07 ` Nathanael Nerode
2002-04-02 12:14 ` Nathanael Nerode
2002-04-02 12:23 ` Daniel Jacobowitz
2002-04-02 12:04 ` Daniel Jacobowitz [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=20020402150500.B8031@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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