From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] README: update
Date: Mon, 2 Sep 2019 11:09:49 +0200 [thread overview]
Message-ID: <20190902090949.GE13226@pengutronix.de> (raw)
In-Reply-To: <20190902102340.3a697315@litschi.hi.pengutronix.de>
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:
> > When reading this README, the tarball was obviously already extracted,
> > so remove the very unclear section about how to get it. Anyway, anything
> > important is in the manual, which is linked later.
>
> I agree that the section is unclear, but the README can be read from
> the git webview, too. Maybe this section should be rewritten for the
> viewpoint of a git user?
I think it can be removed. This section used to contain multiple archives
that had to be downloaded but all others are gone now.
> >
> > TODO is no longer there since commit b710f8cdf410a91b4298 ("PTXdist:
> > remove useless and unmaintained files").
> >
> > Link to the new documentation directly instead of through a redirected
> > URL, and fix incorrect use of "refer" in the section heading.
> >
> > Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> > ---
> > README | 20 +++++---------------
> > 1 file changed, 5 insertions(+), 15 deletions(-)
> >
> > diff --git a/README b/README
> > index 33cf90e0bc19..608b4749bdcd 100644
> > --- a/README
> > +++ b/README
> > @@ -1,15 +1,6 @@
> > PTXdist
> > =======
> >
> > -Necessary Packages
> > -------------------
> > -
> > -In order to build ptxdist, you need this archive:
> > -
> > - ptxdist-<version>.tgz
> > -
> > -Extract this archive into some build directory.
> > -
> > Installation
> > ------------
> >
> > @@ -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.
Michael
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-09-02 9:09 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 [this message]
2019-09-02 11:36 ` Ladislav Michl
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=20190902090949.GE13226@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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