From: sms@2BSD.COM (Steven M. Schultz)
Subject: [pups] Success!
Date: Tue, 25 Feb 2003 10:07:55 -0800 (PST) [thread overview]
Message-ID: <200302251807.h1PI7tS29457@moe.2bsd.com> (raw)
> From: David Evans <dfevans at bbcr.uwaterloo.ca>
> > Now it looks like all I have left to do is install 400 odd patches.
>
> If somebody goes through this pain, any chance of making a new source kit?
Most of the kits I've seen out there are around #430 or so - that
only leaves a dozen or so patches that need to be applied.
> Though I guess some of the patches are not necessarily desirable in all
> circumstances...
By and large they are not only desirable but necessary/mandatory. There
are very few 'frivolous' ("gee, this looks like fun") patches in the
batch. Trying to "pick and choose" which parts of which patches to
apply might be doable in the short term but there _will_ come the
day when a bug is encountered or a feature desired that was fixed or
added as one of the parts/patches that was left out. Best to get
the pain over _once_ and be done with it ;)
Cheers,
Steven Schultz
next reply other threads:[~2003-02-25 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 18:07 Steven M. Schultz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-25 20:01 Fred N. van Kempen
2003-02-25 18:02 Steven M. Schultz
2003-02-25 17:05 Christopher McNabb
2003-02-25 17:35 ` David Evans
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=200302251807.h1PI7tS29457@moe.2bsd.com \
--to=sms@2bsd.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 NNTP newsgroup(s).