> On Sat, 17 Aug 2019, Michał Górny wrote:
> Here's v2 of my proposed format. Two changes:
> 1. I've changed the 'header line' to start with '#!', so comment
> stripping normally takes care of it without having to do extra work.
> 2. I've allowed Markdown syntax in note field, so that we
On Sat, 2019-08-17 at 09:06 +0200, Michał Górny wrote:
> Hi,
>
> Here's v2 of my proposed format.
Also example usage:
get user/group named 'adm'
$ awk '$1 == "adm"' uid-gid.txt
adm 3 4 baselayout
get records for UID 3:
$ awk '$2 == 3' uid-gid.txt
adm
Hi,
Here's v2 of my proposed format. Two changes:
1. I've changed the 'header line' to start with '#!', so comment
stripping normally takes care of it without having to do extra work.
2. I've allowed Markdown syntax in note field, so that we can link
commits similarly to how we do it on wiki.
On Mon, 12 Aug 2019 11:20:01 -0700
Alec Warner wrote:
> > And both of those can have "Fun" merge conflict issues due to the
> > requirements around record delimiters and syntax,
> >
>
> And this means what? That I might check something in that is broken?
> How is this not true for any syntax
On Mon, 12 Aug 2019 11:20:01 -0700
Alec Warner wrote:
> >
> > As for JSON/YAML, ... eh... that may be the case for like, 4 line files.
> >
> > But once you have hundreds of entries, that becomes less true.
> >
>
> What becomes less true?
In that it ceases to be a human-editable format.
Its
On Mon, Aug 12, 2019 at 10:58 AM Kent Fredric wrote:
> On Mon, 12 Aug 2019 09:52:40 -0700
> Alec Warner wrote:
>
> > CSV, JSON and YAML are both popular machine-and-people readable
> > specifications with broad support.
>
> No, not CSV. There isn't really "a spec" for that. Even though there is
On Mon, 12 Aug 2019 09:52:40 -0700
Alec Warner wrote:
> CSV, JSON and YAML are both popular machine-and-people readable
> specifications with broad support.
No, not CSV. There isn't really "a spec" for that. Even though there is
a "proposed spec", "CSV editors" and things that emit CSV just
On Sun, 11 Aug 2019 17:53:44 -0500
William Hubbs wrote:
> , since he says we can add more fields in the future,
> you either have to escape whitespace in the notes field or quote the
> field.
This was originally what I was going to comment on when the proposal
first hit the list.
But then I
On Sun, Aug 11, 2019 at 7:51 PM Michał Górny wrote:
> On Sun, 2019-08-11 at 17:53 -0500, William Hubbs wrote:
> > On Sun, Aug 11, 2019 at 03:04:02PM -0700, Matt Turner wrote:
> > > On Sun, Aug 11, 2019 at 12:48 PM William Hubbs
> wrote:
> > > > If we are going to require a modeline, shouldn't
On Sun, 2019-08-11 at 17:53 -0500, William Hubbs wrote:
> On Sun, Aug 11, 2019 at 03:04:02PM -0700, Matt Turner wrote:
> > On Sun, Aug 11, 2019 at 12:48 PM William Hubbs wrote:
> > > If we are going to require a modeline, shouldn't we consider allowing
> > > them by default so we can work out of
On Sun, Aug 11, 2019 at 3:54 PM William Hubbs wrote:
>
> On Sun, Aug 11, 2019 at 03:04:02PM -0700, Matt Turner wrote:
> > On Sun, Aug 11, 2019 at 12:48 PM William Hubbs wrote:
> > > If we are going to require a modeline, shouldn't we consider allowing
> > > them by default so we can work out of
On Sun, Aug 11, 2019 at 03:04:02PM -0700, Matt Turner wrote:
> On Sun, Aug 11, 2019 at 12:48 PM William Hubbs wrote:
> > If we are going to require a modeline, shouldn't we consider allowing
> > them by default so we can work out of the box instead of having to tweak
> > our editor settings?
>
>
On Sun, Aug 11, 2019 at 12:48 PM William Hubbs wrote:
>
> On Sat, Aug 10, 2019 at 05:41:56PM -0700, Matt Turner wrote:
> > On Sat, Aug 10, 2019 at 1:49 PM William Hubbs wrote:
> > >
> > > On Tue, Aug 06, 2019 at 11:29:50PM +0200, Michał Górny wrote:
> > > > Hi,
> > > >
> > > > Some time ago
On Sat, Aug 10, 2019 at 05:41:56PM -0700, Matt Turner wrote:
> On Sat, Aug 10, 2019 at 1:49 PM William Hubbs wrote:
> >
> > On Tue, Aug 06, 2019 at 11:29:50PM +0200, Michał Górny wrote:
> > > Hi,
> > >
> > > Some time ago William asked me to move UID/GID assignments from wiki [1]
> > > to
> On Sun, 11 Aug 2019, William Hubbs wrote:
> Well, I suppose it wouldn't be a problem if we don't care about
> alignment, but that is not readable either really right?
> For example, (completely making up uid/gid numbers), this is totally
> valid.
> root 0 0 baselayout this is from
On Sat, Aug 10, 2019 at 1:49 PM William Hubbs wrote:
>
> On Tue, Aug 06, 2019 at 11:29:50PM +0200, Michał Górny wrote:
> > Hi,
> >
> > Some time ago William asked me to move UID/GID assignments from wiki [1]
> > to something more accessible. I've finally gotten around to draft
> > something, and
On Sun, Aug 11, 2019 at 12:40:04AM +0200, Ulrich Mueller wrote:
> > On Sat, 10 Aug 2019, William Hubbs wrote:
>
> > I propose using a colon like we do in /etc/passwd:
>
> > root:0:0:baselayout:
> > bin:1:1:baselayout:some notes go here
>
> Please no. I thought the purpose of this
On Sat, Aug 10, 2019 at 10:51:52PM +0200, Michał Górny wrote:
> On Sat, 2019-08-10 at 15:49 -0500, William Hubbs wrote:
> > On Tue, Aug 06, 2019 at 11:29:50PM +0200, Michał Górny wrote:
> > > Hi,
> > >
> > > Some time ago William asked me to move UID/GID assignments from wiki [1]
> > > to
> On Sat, 10 Aug 2019, William Hubbs wrote:
> I propose using a colon like we do in /etc/passwd:
> root:0:0:baselayout:
> bin:1:1:baselayout:some notes go here
Please no. I thought the purpose of this exercise was to have a format
that is human readable, and not something with strange
On Sat, 2019-08-10 at 15:49 -0500, William Hubbs wrote:
> On Tue, Aug 06, 2019 at 11:29:50PM +0200, Michał Górny wrote:
> > Hi,
> >
> > Some time ago William asked me to move UID/GID assignments from wiki [1]
> > to something more accessible. I've finally gotten around to draft
> > something,
On Tue, Aug 06, 2019 at 11:29:50PM +0200, Michał Górny wrote:
> Hi,
>
> Some time ago William asked me to move UID/GID assignments from wiki [1]
> to something more accessible. I've finally gotten around to draft
> something, and I'd like to hear your comments about it. The idea is to
> keep a
Hi,
Some time ago William asked me to move UID/GID assignments from wiki [1]
to something more accessible. I've finally gotten around to draft
something, and I'd like to hear your comments about it. The idea is to
keep a whitespace-separated record format file in api.gentoo.org repo.
This is
22 matches
Mail list logo
