Re: [gentoo-dev] On banning merge commits

Don't be crazy - I know many developer groups which dislike merge commits. That nonlinear work flow is just a mess long term.   Original Message   From: Michał Górny Sent: Sunday, May 8, 2016 13:09 To: Patrice Clement Reply To: gentoo-dev@lists.gentoo.org Cc: gentoo-dev@lists.gentoo.org Subject:

[gentoo-dev] News Item: LastPass package migration

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Title: LastPass package migration Author: Robin H. Johnson Content-Type: text/plain Posted: 2016-05-08 Revision: 1 News-Item-Format: 1.0 Display-If-Installed: app-admin/lastpass LastPass-3 and earlier versions installed browser

Re: [gentoo-dev] On banning merge commits

On Sun, 8 May 2016 01:52:22 +0200 Patrice Clement wrote: > Hi gents > > After yet another discussion about git in the #gentoo-dev channel tonight, the > topic of merge commits came up for the umpteenth time. > > We all seem to agree merge commits are really bad design,

Re: [gentoo-dev] [PATCH] l10n.eclass: Sort and normalize PLOCALES in l10n_find_plocales_change

On Sat, May 7, 2016 at 11:23 PM, James Le Cuirot wrote: > On Sat, 7 May 2016 23:13:11 +0200 > Davide Pesavento wrote: > >> On Sat, May 7, 2016 at 10:13 PM, James Le Cuirot >> wrote: >> > l10n_find_plocales_change assumes that PLOCALES is

[gentoo-dev] On banning merge commits

Hi gents After yet another discussion about git in the #gentoo-dev channel tonight, the topic of merge commits came up for the umpteenth time. We all seem to agree merge commits are really bad design, add clutter to the log graph after a while and should be banned altogether from reaching the

[gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sat, 7 May 2016 23:25:58 +0200 Michał Górny wrote: > On Sat, 7 May 2016 21:19:31 + (UTC) > "Joerg Bornkessel" wrote: > > > commit: 66afcab271f65b97330e610040ad3acc1b812a03 > > Author: Joerg Bornkessel gentoo org> > > AuthorDate: Sat

[gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sat, 7 May 2016 21:19:31 + (UTC) "Joerg Bornkessel" wrote: > commit: 66afcab271f65b97330e610040ad3acc1b812a03 > Author: Joerg Bornkessel gentoo org> > AuthorDate: Sat May 7 21:18:48 2016 + > Commit: Joerg Bornkessel gentoo org> > CommitDate: Sat

Re: [gentoo-dev] [PATCH] l10n.eclass: Sort and normalize PLOCALES in l10n_find_plocales_change

On Sat, 7 May 2016 23:13:11 +0200 Davide Pesavento wrote: > On Sat, May 7, 2016 at 10:13 PM, James Le Cuirot > wrote: > > l10n_find_plocales_change assumes that PLOCALES is sorted > > alphanumerically with a single space between each entry and no > >

[gentoo-portage-dev] [PATCH 3/3] xml-test/uniqueness: tests for unique (element,attribute,value) combinations

Signed-off-by: Göktürk Yüksek --- xml-test/uniqueness/metadata.xml | 33 +++ xml-test/uniqueness/uniqueness-0.1.ebuild | 12 +++ 2 files changed, 45 insertions(+) create mode 100644 xml-test/uniqueness/metadata.xml create

[gentoo-portage-dev] [PATCH 2/3] xml-test/singularity: tests for at-most-one element violations

Signed-off-by: Göktürk Yüksek --- xml-test/singularity/metadata.xml | 43 + xml-test/singularity/singularity-0.1.ebuild | 11 2 files changed, 54 insertions(+) create mode 100644 xml-test/singularity/metadata.xml create

[gentoo-portage-dev] [PATCH 1/3] xml-text/valid: add a second description to downstream maintainer

Increase coverage and prevent future regressions by adding a second description for a downstream maintainer element. See also: https://gitweb.gentoo.org/data/xml-schema.git/commit/?id=6070512ca Signed-off-by: Göktürk Yüksek --- xml-test/valid/metadata.xml | 1 + 1 file

Re: [gentoo-dev] [PATCH] l10n.eclass: Sort and normalize PLOCALES in l10n_find_plocales_change

On Sat, May 7, 2016 at 10:13 PM, James Le Cuirot wrote: > l10n_find_plocales_change assumes that PLOCALES is sorted > alphanumerically with a single space between each entry and no > surrounding whitespace. This is not a bad assumption but it isn't > documented and it's

[gentoo-dev] [PATCH] l10n.eclass: Sort and normalize PLOCALES in l10n_find_plocales_change

l10n_find_plocales_change assumes that PLOCALES is sorted alphanumerically with a single space between each entry and no surrounding whitespace. This is not a bad assumption but it isn't documented and it's inconvenient in at least one particular case. MakeMKV uses non-standard locale names and I

Re: [gentoo-dev] amd64 and x32 systemd stages should be ready

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Samstag, 7. Mai 2016, 19:47:55 schrieb Andreas K. Huettel: > Am Samstag, 7. Mai 2016, 17:09:50 schrieb Anthony G. Basile: > > Hi everyone, > > > > I've been pushing out systemd stage3s for amd64 and x86 and putting them > > under our official

Re: [gentoo-dev] amd64 and x32 systemd stages should be ready

On 5/7/16 1:47 PM, Andreas K. Huettel wrote: > Am Samstag, 7. Mai 2016, 17:09:50 schrieb Anthony G. Basile: >> Hi everyone, > >> I've been pushing out systemd stage3s for amd64 and x86 and putting them >> under our official releases at [1] and [2]. I think all the bugs are >> out and those

Re: [gentoo-dev] amd64 and x32 systemd stages should be ready

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Samstag, 7. Mai 2016, 17:09:50 schrieb Anthony G. Basile: > Hi everyone, > > I've been pushing out systemd stage3s for amd64 and x86 and putting them > under our official releases at [1] and [2]. I think all the bugs are > out and those stages

Re: [gentoo-dev] amd64 and x32 systemd stages should be ready

On 07/05/16 16:09, Anthony G. Basile wrote: > Hi everyone, > > I've been pushing out systemd stage3s for amd64 and x86 and putting them > under our official releases at [1] and [2]. I think all the bugs are > out and those stages are pretty tight. The next step is for me to > advertise them at

[gentoo-dev] amd64 and x32 systemd stages should be ready

Hi everyone, I've been pushing out systemd stage3s for amd64 and x86 and putting them under our official releases at [1] and [2]. I think all the bugs are out and those stages are pretty tight. The next step is for me to advertise them at [3]. So this is just a heads up. Let me know if I