Archives
Archives
| From: | Alessandro Barbieri <lssndrbarbieri@×××××.com> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Subject: | Re: [gentoo-dev] New tool: merge-driver-ekeyword automatically resolves git merge conflicts involving KEYWORDS=... | ||
| Date: | Tue, 02 Mar 2021 19:36:38 | ||
| Message-Id: | CACfyCdUctBZxEJ-djhbZ=bAptmB0M8T7oCnhBStzo7azwb6aYA@mail.gmail.com | ||
| In Reply to: | Re: [gentoo-dev] New tool: merge-driver-ekeyword automatically resolves git merge conflicts involving KEYWORDS=... by Matt Turner |
||
| 1 | Il Mar 2 Mar 2021, 20:03 Matt Turner <mattst88@g.o> ha scritto: |
| 2 | |
| 3 | > On Tue, Mar 2, 2021 at 12:11 AM Michael Orlitzky <mjo@g.o> wrote: |
| 4 | > > why don't we just enforce putting each |
| 5 | > > keyword on a separate line instead, so that we don't have this problem |
| 6 | > > in the first place? |
| 7 | > |
| 8 | > Why don't we change 30 thousand ebuilds rather than use this script? |
| 9 | > |
| 10 | |
| 11 | IMO before this the keyword mechanism should be reworked to be three-state: |
| 12 | 1 Arch known working |
| 13 | 2 Arch known not working |
| 14 | 3 Arch untested/status unknown |
| 15 | |
| 16 | And let the user choose to use packages from 3 or not |
| Subject | Author |
|---|---|
| Re: [gentoo-dev] New tool: merge-driver-ekeyword automatically resolves git merge conflicts involving KEYWORDS=... | Brian Evans <grknight@g.o> |
| Re: [gentoo-dev] New tool: merge-driver-ekeyword automatically resolves git merge conflicts involving KEYWORDS=... | Matt Turner <mattst88@g.o> |