| 1 |
W dniu wto, 09.01.2018 o godzinie 11∶15 -0500, użytkownik Alec Warner |
| 2 |
napisał: |
| 3 |
> On Tue, Jan 9, 2018 at 10:11 AM, Alec Warner <antarus@g.o> wrote: |
| 4 |
> |
| 5 |
> > |
| 6 |
> > On Tue, Jan 9, 2018 at 9:43 AM, Michał Górny <mgorny@g.o> wrote: |
| 7 |
> > |
| 8 |
> > > Add @MAINTAINER comments before each profile set indicating |
| 9 |
> > > the effective maintainer for the following set of profiles. While most |
| 10 |
> > > of those entries may seem obvious at first, I expect that some |
| 11 |
> > > of the sub-profiles will eventually 'change hands', e.g. the /hardened |
| 12 |
> > > sub-profiles would be maintained by Hardened, etc. |
| 13 |
> > > |
| 14 |
> > > The main goal is to provide a clear indication of who maintains each |
| 15 |
> > > profile. This will be of great help both to bug-wranglers (who currently |
| 16 |
> > > have to pretty much guess who to assign profile bugs to) and to other |
| 17 |
> > > developers who plan to commit larger changes and want to get ACK from |
| 18 |
> > > appropriate parties. |
| 19 |
> > > --- |
| 20 |
> > > profiles/profiles.desc | 23 +++++++++++++++++++++++ |
| 21 |
> > > 1 file changed, 23 insertions(+) |
| 22 |
> > > |
| 23 |
> > > diff --git a/profiles/profiles.desc b/profiles/profiles.desc |
| 24 |
> > > index 66dd7a32799f..8c9bd78143a1 100644 |
| 25 |
> > > --- a/profiles/profiles.desc |
| 26 |
> > > +++ b/profiles/profiles.desc |
| 27 |
> > > @@ -7,6 +7,7 @@ |
| 28 |
> > > #arch profile_directory status |
| 29 |
> > > |
| 30 |
> > > # Alpha Profiles |
| 31 |
> > |
| 32 |
> > |
| 33 |
> > How are machines supposed to read this data? |
| 34 |
> > Can we consider structured data? |
| 35 |
> > |
| 36 |
> |
| 37 |
> Sorry using more words: |
| 38 |
> |
| 39 |
> Currently the data is 'structured' in that its space separated data; and |
| 40 |
> you can probably use basic csv parsers to get at it (but not comments.) Now |
| 41 |
> we are adding a maintainer field. But its in a comment (so machines can't |
| 42 |
> read it). So how will machines read this data; or just make an explicit |
| 43 |
> goal that machines shouldn't. |
| 44 |
> |
| 45 |
|
| 46 |
Similar to eclassdoc. Grep for @MAINTAINER comment preceding |
| 47 |
the profile, read the line and grab e-mail address(es). |
| 48 |
|
| 49 |
This is a non-obligatory extension. We can't change the file format |
| 50 |
without breaking existing tools. Comments are safe. |
| 51 |
|
| 52 |
-- |
| 53 |
Best regards, |
| 54 |
Michał Górny |
Archives