Re: How to cope with patches sanely
- To: debian-devel@lists.debian.org
- Subject: Re: How to cope with patches sanely
- From: martin f krafft <madduck@madduck.net>
- Date: Sat, 2 Feb 2008 17:36:40 +1100
- Message-id: <[🔎] 20080202063640.GA10752@lapse.madduck.net>
- Mail-followup-to: debian-devel@lists.debian.org
- In-reply-to: <20080126162316.GB5582@artemis.madism.org>
- References: <20080124084047.GA2868@piper.oerlikon.madduck.net> <87fxwmiuj3.fsf@windlord.stanford.edu> <alpine.DEB.1.00.0801250818360.5187@wr-linux02> <20080125080158.GC5185@dario.dodds.net> <alpine.DEB.1.00.0801250937390.5187@wr-linux02> <1201252109.4297.13.camel@shizuru> <k31s65-fm5.ln1@argenau.downhill.at.eu.org> <20080126162316.GB5582@artemis.madism.org>
also sprach Pierre Habouzit <madcoder@debian.org> [2008.01.27.0323 +1100]:
> For example when you need different series of patches per
> architecture (the libc e.g. has specific hurd patches).
Wouldn't this be handled better with preprocessor #ifdefs? I'd say
it would make the code clearer and more maintainable. But then
again, I have none (read: zero) experience with this sort of
challenge.
--
martin | http://madduck.net/ | http://two.sentenc.es/
"life moves pretty fast. if you don't stop and look around once in
a while, you could miss it."
-- ferris bueller
spamtraps: madduck.bogus@madduck.net
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
Reply to: