From: Andreas Schwab <schwab@suse.de>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Refactor bpstat_stop_status.
Date: Sun, 16 Dec 2007 18:46:00 -0000 [thread overview]
Message-ID: <je63yy32do.fsf@sykes.suse.de> (raw)
In-Reply-To: <200712162115.00462.vladimir@codesourcery.com> (Vladimir Prus's message of "Sun\, 16 Dec 2007 21\:14\:59 +0300")
Vladimir Prus <vladimir@codesourcery.com> writes:
> The bpstat_stop_status function is rather big today,
> which makes it hard to do further changes. This patch
> extracts bits of that function into separate functions.
> No changes in behaviour are expected, and no regressions. OK?
Could you please add a comment before each function that summerizes
their purpose?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-12-16 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 18:38 Vladimir Prus
2007-12-16 18:46 ` Andreas Schwab [this message]
2007-12-16 20:05 ` Vladimir Prus
2007-12-17 0:01 ` Daniel Jacobowitz
2008-04-24 14:08 ` Vladimir Prus
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=je63yy32do.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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