public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org, scarabeus@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-office/libreoffice: ChangeLog libreoffice-3.4.99.1.ebuild libreoffice-3.5.0.0.ebuild
Date: Fri, 16 Dec 2011 20:33:11 +0000	[thread overview]
Message-ID: <4EEBAB07.2010102@gentoo.org> (raw)
In-Reply-To: <20111212174448.F09FC2004B@flycatcher.gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 12/12/2011 05:44 PM, Tomas Chvatal (scarabeus) wrote:
> scarabeus    11/12/12 17:44:48
> 
> Modified:             ChangeLog Added:
> libreoffice-3.4.99.1.ebuild Removed:
> libreoffice-3.5.0.0.ebuild Log: Remove miss-named beta0. Add beta1
> with better name (presented as downgrade).
> 
> (Portage version: 2.2.0_alpha80/cvs/Linux x86_64, RepoMan options:
> --force)
> 
> Revision  Changes    Path 1.216
> app-office/libreoffice/ChangeLog
> 
I know it is a bit late but do you think that commit made sense at
that time? It is not the best user experience we can provide when beta
releases appear as downgrades. FWIW beta releases should remain masked
to avoid useless compilations to slow machines instead of digging
through Changelogs to see what happened. Are the beta releases of
libreoffice so critical that force you to keep them in the ~testing tree?

- -- 
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iQIcBAEBCgAGBQJO66sGAAoJEPqDWhW0r/LCSH0QAIKc26at3BPsEauv1Wk/6hir
lfrFv0BEDgIUHwi4vFQT6xUTCYpC83Ed2wTXG7wHj2HVh2pIqnRPitvOwKYL6b7/
HCRnGo8jm8Hg906nJEPPCDJxAL34U4qaO4Lt2+cTU5g1ifxYsG8FP97gp2O18OmV
CQBkacsjtpwngrZkTjonD+eeHjzoXMOXP9MWdkBwBWAEhqkkHDYjGfXKZ5byhD1j
FdkKCkmKKVaCFdxbsRfMxnNEhkxQFbvmejmXKi6nrpnkWWz9c+CAm6A9btLx8FOU
qop7UTRMVptMJGOWqgMV+FI/TB1Rfl/yBiq40D1FAdAcA3SdmqP3zI6Ee5PakBBo
5o49nv/DUgkv53VH1T5THyixQAv+Fcsv7caCPc91HSMPgC8YvyKwXRuks+WyFcNp
UApstSl5ESOxOl2VUeUebKEbQmHgRZduSqzauFrGGHI+dUSPhFgvAuS8JZuAbadF
XV5S/Pca8HUIYKf1jMfgDRwMXXnO7cNYm6HyIoYPmXaicfxAry0Bomd8HC4ZAfET
0FC9Ushx1kI4SeWp7TxXc0mtreOhtj7GkiUQf5RWpa0TNikSC5Qz21Xt3HX56YL/
MBhyrCNkb8s0YZeeNLxnQFnrANuJqGRRVPtGpCaS0lKe2MVekjBFQWXZGuWcaiFC
qXK+RAqBEGam86hw2Keh
=+H4t
-----END PGP SIGNATURE-----



       reply	other threads:[~2011-12-16 20:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111212174448.F09FC2004B@flycatcher.gentoo.org>
2011-12-16 20:33 ` Markos Chandras [this message]
2011-12-17  8:32   ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-office/libreoffice: ChangeLog libreoffice-3.4.99.1.ebuild libreoffice-3.5.0.0.ebuild Ciaran McCreesh
2011-12-17 10:47     ` Markos Chandras
2011-12-17 12:02       ` Ciaran McCreesh
2011-12-17 16:58         ` Zac Medico
     [not found]   ` <CA+NrkpcuKrmKV3ySvc3_TwWVvD6Y6D78O1K6hBXCcx65s1SVTw@mail.gmail.com>
2011-12-17  9:56     ` Markos Chandras
2011-12-17 10:27       ` Pacho Ramos

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=4EEBAB07.2010102@gentoo.org \
    --to=hwoarang@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=scarabeus@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