public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-core@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Gentle reminder about ChangeLog entries on profiles
Date: Mon, 08 Jan 2007 08:27:50 -0500	[thread overview]
Message-ID: <1168262870.787.2.camel@vertigo.twi-31o2.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

Most of the profiles under default-linux have a ChangeLog at the
architecture level.  If you make *any* changes to a profile, you should
be putting your changes in the ChangeLog.

For example, if you edit
profiles/default-linux/amd64/2006.1/no-multilib/package.mask, then you
need to add an entry at profiles/default-linux/amd64/ChangeLog.  You can
use echangelog, which works perfectly fine.  Being unable to easily
track changes in profiles makes Release Engineering (and arch teams)
cry, so please add a ChangeLog entry, or we'll sick Jeff and the goats
on you.

Thanks,

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2007-01-08 13:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 13:27 Chris Gianelloni [this message]
2007-01-08 20:20 ` [gentoo-dev] Gentle reminder about ChangeLog entries on profiles Robin H. Johnson
2007-01-08 22:40   ` Chris Gianelloni
2007-01-08 23:11     ` Chris Gianelloni
2007-01-08 23:43     ` Ned Ludd
2007-01-08 23:50       ` Diego 'Flameeyes' Pettenò
2007-01-08 23:52       ` Robin H. Johnson
2007-01-09 18:59         ` Chris Gianelloni
2007-01-09  3:34   ` Luca Barbato
2007-01-09  5:03     ` Mike Doty

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=1168262870.787.2.camel@vertigo.twi-31o2.org \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-core@lists.gentoo.org \
    --cc=gentoo-dev@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