Hi,
I created a very basic script which should be extended to show all
hardware information needed. Once that works I'd package it.
https://forum.openwrt.org/t/script-convert-device-information-to-yaml/53516
Best,
Paul
On 1/12/20 11:47 AM, Paul Spooren wrote:
Hi all,
some time ago I
Hi Paul,
Hi Martin,
On Sun, Jan 12, 2020 at 10:13:42PM -1000, Paul Spooren wrote:
> Hi,
>
> On 1/12/20 1:05 PM, Martin Blumenstingl wrote:
> > Hi Paul,
> >
> > On Sun, Jan 12, 2020 at 10:47 PM Paul Spooren wrote:
> > > Hi all,
> > >
> > > some time ago I created a (now outdated) device
On 1/13/20 3:03 AM, Thomas Endt wrote:
-Ursprüngliche Nachricht-
Von: openwrt-devel Im
Auftrag von Paul Spooren
Gesendet: Sonntag, 12. Januar 2020 22:47
An: 'OpenWrt Development List'
Betreff: [OpenWrt-Devel] [RFC] commit message in YAML format for new
devices
An illustrative commit there
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Paul,
On Mon, Jan 13, 2020 at
> -Ursprüngliche Nachricht-
> Von: openwrt-devel Im
> Auftrag von Paul Spooren
> Gesendet: Sonntag, 12. Januar 2020 22:47
> An: 'OpenWrt Development List'
> Betreff: [OpenWrt-Devel] [RFC] commit message in YAML format for new
> devices
> An illustrative co
ject: Re: [OpenWrt-Devel] [RFC] commit message in YAML format for new
> devices
>
> Paul Spooren [2020-01-12 11:47:29]:
>
> Hi,
>
> > Every commit message for newly added devices must contain a number of
> > hardware information and steps for an initial installation
Paul Spooren [2020-01-12 11:47:29]:
Hi,
> Every commit message for newly added devices must contain a number of
> hardware information and steps for an initial installation.
> The hardware information should contain at least the following information,
> maybe more:
YAML is really PITA, so you
On 13/01/2020 00:05, Martin Blumenstingl via openwrt-devel wrote:
can we automate this somehow?
the device tree files already contain most of that information.
(I'm all for providing good data for the TOH but I'm challenging the
idea of doing this manually)
Martin
Hi,
I think this will turn
Hi,
On 1/12/20 1:05 PM, Martin Blumenstingl wrote:
Hi Paul,
On Sun, Jan 12, 2020 at 10:47 PM Paul Spooren wrote:
Hi all,
some time ago I created a (now outdated) device overview[0] based on
YAML meta data. This approach could simplify maintaining an device
overview and device specific
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Paul,
On Sun, Jan 12, 2020 at
On Sun, 12 Jan 2020 11:47:29 -1000, Paul Spooren wrote:
> All commits adding new devices already include most relevant information
> for creating the overview. However it would be convenient if developers
> would format their commit messages in a generic format, therefore I'd
> propose the
Hi all,
some time ago I created a (now outdated) device overview[0] based on
YAML meta data. This approach could simplify maintaining an device
overview and device specific pages[1].
All commits adding new devices already include most relevant information
for creating the overview. However
12 matches
Mail list logo
