public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [Council] ChangeLog generation within Gentoo
Date: Thu, 27 Oct 2011 06:56:15 +1300	[thread overview]
Message-ID: <CAATnKFCtKg=Fd=ofF88n2CL3-yOVvROzhDc6qqdg13A3ws2CEQ@mail.gmail.com> (raw)
In-Reply-To: <20111026193356.058efef7@neptune.home>

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

On 27 October 2011 06:33, Bruno <bonbons67@internet.lu> wrote:

>
> Is there some guideline about old entries in the ChangeLog?
>
> Over the past months ChangeLogs represent a big part of the tree, some
> of them being pretty big and going back many changes (hundreds of them)
> and years (even for actively maintained ebuilds).
>
>
A lot of the older changelog entries also tend to be less normal, and some
long changelogs are so a-typical its virtually impossible to parse them with
machine code.

I know its probably not a big priority for most people, but if changelogs
can retain consistency so that the only part which is inconsistent is the
messages themselves.

I saw the --echangelog parameter turn up sometime this week and I haven't
played with it for fear of subtle inconsistencies with the form produced by
the echangelog client.

( I've been hacking on various tools to parse/normalise changelogs myself,
but it got overwhelming and I got sidetracked )

-- 
Kent

perl -e  "print substr( \"edrgmaM  SPA NOcomil.ic\\@tfrken\", \$_ * 3, 3 )
for ( 9,8,0,7,1,6,5,4,3,2 );"

http://kent-fredric.fox.geek.nz

[-- Attachment #2: Type: text/html, Size: 1569 bytes --]

  reply	other threads:[~2011-10-26 17:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 17:02 [gentoo-dev] [Council] ChangeLog generation within Gentoo Fabian Groffen
2011-10-26 17:33 ` Bruno
2011-10-26 17:56   ` Kent Fredric [this message]
2011-10-26 18:02     ` Rich Freeman
2011-10-26 21:00       ` Fabian Groffen
2011-10-27  3:28         ` [gentoo-dev] " Duncan
2011-10-27  7:05           ` Fabian Groffen
2011-10-26 18:07   ` [gentoo-dev] " Pacho Ramos
2011-10-26 19:24     ` Bruno
2011-10-26 23:56   ` [gentoo-dev] " Ryan Hill
2011-10-27  7:34   ` [gentoo-dev] " Michael Haubenwallner

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='CAATnKFCtKg=Fd=ofF88n2CL3-yOVvROzhDc6qqdg13A3ws2CEQ@mail.gmail.com' \
    --to=kentfredric@gmail.com \
    --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