From: Matthew Galgoci <mgalgoci@redhat.com>
To: law@redhat.com
Cc: Jason Molenda <jason-swarelist@molenda.com>,
"Joseph S. Myers" <jsm@polyomino.org.uk>,
Christopher Faylor <cgf@redhat.com>,
<overseers@sources.redhat.com>
Subject: Re: brk() bug
Date: Thu, 04 Dec 2003 05:32:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0312040030060.27326-100000@lacrosse.corp.redhat.com> (raw)
In-Reply-To: <200312040332.hB43WGfr017360@speedy.slc.redhat.com>
On Wed, 3 Dec 2003 law@redhat.com wrote:
> In message <20031203160905.A55970@molenda.com>, Jason Molenda writes:
> >On Thu, Dec 04, 2003 at 12:05:47AM +0000, Joseph S. Myers wrote:
> >
> >> no response. This bug (anoncvs can create and delete tags) is still
> >> present. Updates can easily fall through the cracks.
> >
> >
> >Our cvs server is a special case - we have a few local modifications
> >that take time to merge in, and no one has had the time to do that
> >merging.
> >
> >I'm hard pressed to think of any other software we've modified on
> >the system to this extent.
> The second largest subsystem that is customized would be the mail system.
> But I've been pretty happy with the security of qmail :-)
qmail could certainly be packaged and tossed into fedora. I'm also a fan
of postfix and exim. postfix has been shipped for a while in rhl, exim is
about to be added to fedora (I think).`
Most fedora packages are just an rpm --rebuild away from whatever target
platform you want them to run on.
--
Matthew Galgoci
System Administrator
Red Hat, Inc
919.754.3700 x44155
next prev parent reply other threads:[~2003-12-04 5:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 19:27 Matthew Galgoci
2003-12-02 19:36 ` law
2003-12-02 19:41 ` Christopher Faylor
2003-12-04 0:05 ` Joseph S. Myers
2003-12-04 0:09 ` Jason Molenda
2003-12-04 1:06 ` Christopher Faylor
2003-12-04 4:27 ` law
2003-12-04 4:27 ` law
2003-12-04 4:27 ` Christopher Faylor
2003-12-04 5:32 ` Matthew Galgoci [this message]
2003-12-04 6:04 ` Jonathan Larmour
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=Pine.LNX.4.44.0312040030060.27326-100000@lacrosse.corp.redhat.com \
--to=mgalgoci@redhat.com \
--cc=cgf@redhat.com \
--cc=jason-swarelist@molenda.com \
--cc=jsm@polyomino.org.uk \
--cc=law@redhat.com \
--cc=overseers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).