From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Richardson,
Bruce" <bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Why rte_snprintf at all?
Date: Tue, 24 Jun 2014 11:22:12 +0200 [thread overview]
Message-ID: <1464235.EKIaBTSv1Q@xps13> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B02CEE1C5C-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-23 22:53, Richardson, Bruce:
> As for the #define, it's a quick fix, except that we end up having to keep
> it forever as the code using the function will never get changed to use
> rte_snprintf. Given it's just a one-line macro, it's probably not a big
> deal in this case, but I'd rather see us take the approach that after
> something has been flagged as deprecated for a certain amount of time e.g.
> 1 to 2 full release cycles, it is removed completely and deleted. Otherwise
> I worry about us having to maintain a bunch of stuff for legacy reasons,
> that really should be got rid of. We should not just remove something
> completely in a single release, but I think we need to have a way to remove
> things completely once the user has been given sufficient warning.
I agree.
--
Thomas
prev parent reply other threads:[~2014-06-24 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 17:16 Why rte_snprintf at all? Stephen Hemminger
[not found] ` <20140623101603.54a5d887-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2014-06-23 22:18 ` Richardson, Bruce
[not found] ` <59AF69C657FD0841A61C55336867B5B02CEE0C0E-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-23 22:25 ` Rogers, Gerald
[not found] ` <CFCDF705.57A9D%gerald.rogers-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-06-23 22:31 ` Wiles, Roger Keith
[not found] ` <AA49F83C-6C0A-45DD-B3D4-5D12BCFA9D49-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
2014-06-23 22:34 ` Richardson, Bruce
[not found] ` <59AF69C657FD0841A61C55336867B5B02CEE1C3A-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-23 22:46 ` Wiles, Roger Keith
[not found] ` <E84A4CA4-9026-43E8-81B0-D17EAD1E64E4-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
2014-06-23 22:53 ` Richardson, Bruce
[not found] ` <59AF69C657FD0841A61C55336867B5B02CEE1C5C-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-24 9:22 ` Thomas Monjalon [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=1464235.EKIaBTSv1Q@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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