From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] 2004.3 ChangeLog! (was: 2004.3 infra request. respond or die)
Date: Wed, 27 Oct 2004 10:26:19 -0400 [thread overview]
Message-ID: <1098887179.12001.1.camel@localhost> (raw)
In-Reply-To: <1098808259.18675.5.camel@helen.science.oregonstate.edu>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
On Tue, 2004-10-26 at 09:30 -0700, Donnie Berkholz wrote:
> On Tue, 2004-10-26 at 06:24, Chris Gianelloni wrote:
> > This doesn't mean we don't want you to do your changelog, quite the
> > contrary. An arch-specific ChangeLog is definitely encouraged for all
> > arches. I just wanted to remind everyone that we're planning on having
> > a *release* changelog which should show all changes across all arches
> > for this release.
>
> Is there some way to reduce the duplication of effort here? We all know
> that when the same information has to be duplicated in multiple places,
> some will be out of sync. Take gentoo/misc/herds.xml. There's no way
> that's up to date.
Well, if someone is doing a arch-specific ChangeLog, I was planning on
simply copying and pasting theirs into ours.
--
Chris Gianelloni
Release Engineering - Operational/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-27 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 16:00 [gentoo-releng] 2004.3 infra request. respond or die Jeffrey Forman
2004-10-25 23:43 ` Lars Weiler
2004-10-25 23:49 ` [gentoo-releng] Re: [gentoo-ppc-dev] " Pieter Van den Abeele
2004-10-26 13:24 ` [gentoo-releng] 2004.3 ChangeLog! (was: 2004.3 infra request. respond or die) Chris Gianelloni
2004-10-26 16:30 ` Donnie Berkholz
2004-10-27 14:26 ` Chris Gianelloni [this message]
2004-10-27 23:17 ` John Davis
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=1098887179.12001.1.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=gentoo-releng@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