public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] Call for agenda items -- Council meeting 2011-11-08
Date: Wed, 26 Oct 2011 15:09:46 -0400	[thread overview]
Message-ID: <CAEdQ38ExNaAL8UVZWKBKQXknyk8DXAUhz1KM5Q2W9ZW0pyJumA@mail.gmail.com> (raw)
In-Reply-To: <1319652305.5300.7.camel@belkin4>

On Wed, Oct 26, 2011 at 2:05 PM, Pacho Ramos <pacho@gentoo.org> wrote:
> El mié, 26-10-2011 a las 19:15 +0200, Fabian Groffen escribió:
>> On 26-10-2011 19:11:24 +0200, Michał Górny wrote:
>> > On Wed, 26 Oct 2011 19:06:07 +0200
>> > Fabian Groffen <grobian@gentoo.org> wrote:
>> >
>> > > > 3) one step towards preventing useless ChangeLog entries.
>> > >
>> > > Also this has been discussed and decided upon by the current and
>> > > previous Councils, so also that opinion is unlikely to suddenly
>> > > change.
>> >
>> > I meant the useless ChangeLog messages done by developers on purpose
>> > like 'ignore this'.
>>
>> Oh, you can just edit them, and "fix" the ChangeLog.
>>
>> I hope people will keep on looking for those, and contact the developer
>> in question to ask him/her to change his/her behaviour.
>>
>>
>
> Why don't we try to reach a consensus? Maybe we should be allowed to
> simply run echangelog (or whatever is used) to generate a message like:
>  26 Oct 2011; Pacho Ramos <pacho@gentoo.org> -pangomm-2.26.3.ebuild
>
> And simply that
>
> Pros:
> - People refusing to add a message saying "Drop old" (or similar) could
> be happy with this, as no redundant information is required to be
> written in ChangeLog.
> - Users will still see that a package was removed, as it's indicated
> with "-" previous removed file.
>
> What do you think?
>
> From my point of view, if we don't try to reach a consensus, we will
> expend time on things to enforce a policy that we could probably expend
> on other tasks and, then, maybe all of us should try to stop being so
> strict and try to give in a bit (not sure if it's the way in English to
> say "ceder" :S)

I think that makes a lot of sense.

Matt



  parent reply	other threads:[~2011-10-26 19:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 16:30 [gentoo-project] Call for agenda items -- Council meeting 2011-11-08 Fabian Groffen
2011-10-26 16:35 ` [gentoo-project] Re: [gentoo-dev] " Michał Górny
2011-10-26 16:37   ` Fabian Groffen
2011-10-26 16:49     ` Michał Górny
2011-10-26 17:06       ` Fabian Groffen
2011-10-26 17:11         ` Michał Górny
2011-10-26 17:15           ` Fabian Groffen
     [not found]             ` <1319652305.5300.7.camel@belkin4>
2011-10-26 19:09               ` Matt Turner [this message]
2011-10-26 20:58               ` Fabian Groffen
2011-10-26 21:03                 ` Chí-Thanh Christopher Nguyễn
2011-10-26 21:07                   ` Fabian Groffen
2011-10-26 22:13                     ` Chí-Thanh Christopher Nguyễn
2011-10-27  7:08                       ` Fabian Groffen
2011-10-26 16:50   ` Markos Chandras
2011-10-31  6:43   ` Peter Volkov
2011-10-31  8:14     ` Michał Górny
2011-10-31  8:27       ` Peter Volkov
2011-10-31  9:52 ` [gentoo-project] " Petteri Räty
2011-10-31 10:27   ` Ulrich Mueller
2011-11-01 21:07     ` Petteri Räty

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=CAEdQ38ExNaAL8UVZWKBKQXknyk8DXAUhz1KM5Q2W9ZW0pyJumA@mail.gmail.com \
    --to=mattst88@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-project@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