mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Issue with install_node creating pipes
Date: Fri, 24 Mar 2017 17:37:01 +0100	[thread overview]
Message-ID: <20170324163701.ccsg7jbdo4aq6jzq@pengutronix.de> (raw)
In-Reply-To: <94D4A88F8AC34646A5288D11318F5D5B24B187F3@GDUKADH841.uk1.r-org.net>

Hi,

On Tue, Mar 14, 2017 at 02:16:05PM +0000, jon.bird@gd-ms.uk wrote:
> On 2017-03-09, Roland Hieber wrote:
> 
> > On 09.03.2017 15:20, jon.bird@gd-ms.uk wrote:
> >>> I think ptxdist-2015.01.0-42-g15c165d69929 broke this. I'm suprised
> >>> nobody notices before. Can you try without this change?
> >>> You can just copy the script to the same location in your BSP and
> >>> change it there.
> >>> 
> >>> Michael
> >>> 
> >> Can you give me a quick crash course on how to do this? Aside from
> >> doing the odd checkout from git, I'm totally unfamiliar with it
> >> having more of a svn background...
> > 
> > Here's what you need to know:
> > 
> > *  To get around firewalls (hopefully), clone the repository via https:
> > 
> >         git clone https://git.pengutronix.de/git/ptxdist
> >         cd ptxdist
> [...]
> 
> Many thanks for that, was very useful. I can confirm that this change did
> cause this issue to arise. Copying this older version in doesn't quite work
> though because there are other changes in there which cause it to fail but
> just backing out that one change in the existing version does.

This should be fixed in master now.

Michael

-- 
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

      reply	other threads:[~2017-03-24 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02  8:25 jon.bird
2017-03-08 10:07 ` Michael Olbrich
2017-03-09 14:20   ` jon.bird
     [not found]     ` <8013bd45-7b84-9429-83b6-db1413731d24@rohieb.name>
2017-03-14 14:16       ` jon.bird
2017-03-24 16:37         ` Michael Olbrich [this message]

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=20170324163701.ccsg7jbdo4aq6jzq@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