From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] [PATCH 5/5] MAINTAINERS: refactor file for easier processing
Date: Wed, 24 Jul 2013 07:57:52 +0200 [thread overview]
Message-ID: <20130724075752.73b2837e@lilith> (raw)
In-Reply-To: <CAP9ODKp2HLj=2B__-hC=RUvLEiYwRzL3tYcVe7XRR_Ogduvg_A@mail.gmail.com>
Hi Otavio,
On Tue, 23 Jul 2013 17:51:27 -0300, Otavio Salvador
<otavio@ossystems.com.br> wrote:
> Hello Albert,
>
> First I'd like to say I do like this change and it can improve a lot
> how tools can make "The Right Thing" automatically (here patman comes
> to my head).
Mailing maintainers is the first use I had in mind, actually, and
patman could indeed do this and benefit from a scriptable way of
finding a board's maintainer(s). But I'm sure other uses will crop up
once the file is there.
> On Tue, Jul 23, 2013 at 5:29 PM, Albert ARIBAUD
> <albert.u.boot@aribaud.net> wrote:
> > +# Note: list sorted by architecture, name, status and maintainer e-mail #
> > +# To keep the list sorted and formatted, you can use the following vi #
> > +# commands, each time placing the cursor on the headers line: #
> > +# #
> > +# :.,$s/\([^ ]*\) \+\([^ ]*\) \+\([^ ]*\) \+\(.*\)/\1:\2:\3:\4/ #
> > +# :.,$!column -s ':' -t #
> > +# :.+1,$!sort #
> > +# #
>
> So I miss a way of doing same sorting and format using shell script. I
> am not a 'vi' user (but an Emacs one) but I think the most generic way
> would be to provide a shell line, or script, for it.
Understood. I'll look into adding a shell (bash, unless a war erupts
about this choice) script and referring to it from the file header in
addition to the vi commands. I welcome -- but will hardly be able to
test -- equivalent emacs commands from emacs octopi :) out here.
Same could be done to boards.cfg, BTW, maybe even in a single script
for both files, so I'll probably expand the scope of this submission
to boards.cfg.
> Regards,
>
> --
> Otavio Salvador O.S. Systems
Thanks for your comments!
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-07-24 5:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 20:28 [U-Boot] [RFC] [PATCH 0/5] Refactor MAINTAINERS file Albert ARIBAUD
2013-07-23 20:28 ` [U-Boot] [RFC] [PATCH 1/5] MAINTAINERS: move ARM entries into ARM section Albert ARIBAUD
2013-07-23 20:28 ` [U-Boot] [RFC] [PATCH 2/5] MAINTAINERS: move improperly placed e-mail addresses Albert ARIBAUD
2013-07-23 20:28 ` [U-Boot] [RFC] [PATCH 3/5] MAINTAINERS: remove misplaced comments Albert ARIBAUD
2013-07-23 20:29 ` [U-Boot] [RFC] [PATCH 4/5] MAINTAINERS: remove useless 'header' lines Albert ARIBAUD
2013-07-23 20:29 ` [U-Boot] [RFC] [PATCH 5/5] MAINTAINERS: refactor file for easier processing Albert ARIBAUD
2013-07-23 20:51 ` Otavio Salvador
2013-07-24 5:57 ` Albert ARIBAUD [this message]
2013-07-24 4:34 ` [U-Boot] [RFC] [PATCH 0/5] Refactor MAINTAINERS file Wolfgang Denk
2013-07-25 10:11 ` Albert ARIBAUD
2013-07-26 21:37 ` [U-Boot] [RFC V2 0/9] " Albert ARIBAUD
2013-07-26 21:37 ` [U-Boot] [RFC V2 1/9] MAINTAINERS: move ARM entries into ARM section Albert ARIBAUD
2013-07-26 21:37 ` [U-Boot] [RFC V2 2/9] MAINTAINERS: move improperly placed e-mail addresses Albert ARIBAUD
2013-07-26 21:37 ` [U-Boot] [RFC V2 3/9] MAINTAINERS: remove misplaced comments Albert ARIBAUD
2013-07-26 21:37 ` [U-Boot] [RFC V2 4/9] MAINTAINERS: remove useless 'header' lines Albert ARIBAUD
2013-07-26 21:37 ` [U-Boot] [RFC V2 5/9] MAINTAINERS: refactor file for easier processing Albert ARIBAUD
2013-07-26 21:37 ` [U-Boot] [RFC V2 6/9] tools: add reformat.py and (temporary merge.py) Albert ARIBAUD
2013-07-26 21:37 ` [U-Boot] [RFC V2 7/9] reformat MAINTAINERS and boards.cfg Albert ARIBAUD
2013-07-26 21:37 ` [U-Boot] [RFC V2 8/9] boards.cfg: merge MAINTAINERS and reformat Albert ARIBAUD
2013-07-26 21:37 ` [U-Boot] [RFC V2 9/9] Changes due to boards.cfg reformat Albert ARIBAUD
2013-08-03 14:24 ` [U-Boot] [RFC V2 0/9] Refactor MAINTAINERS file Albert ARIBAUD
2013-08-05 14:28 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130724075752.73b2837e@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.