From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] README: update
Date: Mon, 2 Sep 2019 13:36:35 +0200 [thread overview]
Message-ID: <20190902113635.GA21184@lenoch> (raw)
In-Reply-To: <20190902090949.GE13226@pengutronix.de>
On Mon, Sep 02, 2019 at 11:09:49AM +0200, Michael Olbrich wrote:
> On Mon, Sep 02, 2019 at 10:23:40AM +0200, Michael Tretter wrote:
> > On Sun, 01 Sep 2019 23:04:56 +0200, Roland Hieber wrote:
[...]
> > > @@ -107,15 +98,14 @@ Bugs
> > > ----
> > >
> > > - search for FIXMEs
> > > -- see TODO
> > >
> > > -For documentation please refer:
> > > --------------------------------
> > > +For documentation please refer to:
> > > +----------------------------------
> > >
> > > -http://www.pengutronix.de/software/ptxdist/documentation_en.html
> > > +https://www.ptxdist.org/doc
> > >
> > > -For Patch Tagging please refer:
> > > --------------------------------
> > > +For Patch Tagging please refer to:
> > > +----------------------------------
> > >
> > > http://dep.debian.net/deps/dep3/
> > >
>
> I think this part should be removed. We don't do it like this anyways and
> either way, the README is not the place for this.
So now it seems README would contain mostly instalation instructions. What
about moving them into INSTALL, rename README.devel to README and be done
with that? :)
ladis
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-09-02 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 21:04 Roland Hieber
2019-09-02 8:23 ` Michael Tretter
2019-09-02 9:09 ` Michael Olbrich
2019-09-02 11:36 ` Ladislav Michl [this message]
2019-10-16 11:13 ` Roland Hieber
2019-10-16 11:14 ` [ptxdist] [PATCH v2] " Roland Hieber
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=20190902113635.GA21184@lenoch \
--to=ladis@linux-mips.org \
--cc=ptxdist@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox