public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Dave Nebinger" <dnebinger@joat.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] what's new with all those new packages?
Date: Mon, 11 Jul 2005 13:03:58 -0400	[thread overview]
Message-ID: <000301c5863a$87834780$5f01010a@jnetlab.lcl> (raw)
In-Reply-To: <5bdc1c8b050711094033e82262@mail.gmail.com>

> A number of times
> that I've looked at change logs it turns out that 3 or 4 of these
> changes are to fix things on other architecture while for me they are
> just compile jobs.

Maybe I'm too cynical or maybe it's from experience but in either case I can
tell you as a developer the change log often reflects what I remember I
changed since the last release and is never intended to encompass every
change I made to the source.

>From that perspective the change log provides some helpful ideas about what
changes were implemented but never represents the complete change list.
Making the assumption that it does means that you could end up missing a
critical gentoo security/stability fix.

Besides, if you schedule your compile times for off hours then you really
don't lose anything with the additional compile jobs.



-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-11 17:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 12:34 [gentoo-user] what's new with all those new packages? danielhf
2005-07-11 13:10 ` Philip Webb
2005-07-11 16:20 ` Myk Taylor
2005-07-11 16:40   ` Mark Knecht
2005-07-11 17:03     ` Dave Nebinger [this message]
2005-07-12  6:33     ` Ow Mun Heng
2005-07-11 16:42   ` Roy Wright
2005-07-11 17:08     ` Holly Bostick
2005-07-12 10:35   ` Martin S
2005-07-12 10:45     ` Jason Stubbs

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='000301c5863a$87834780$5f01010a@jnetlab.lcl' \
    --to=dnebinger@joat.com \
    --cc=gentoo-user@lists.gentoo.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