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] [ANNOUNCE] OSELAS.Toolchain() 2012.12.1 released
Date: Wed, 20 Feb 2013 19:00:52 +0100	[thread overview]
Message-ID: <20130220180051.GC5360@pengutronix.de> (raw)
In-Reply-To: <20130216113630.GA26782@regiomontanus.your-server.de>

On Sat, Feb 16, 2013 at 12:36:30PM +0100, Bernhard Walle wrote:
> * Michael Olbrich <m.olbrich@pengutronix.de> [2013-02-15 12:57]:
> > 
> > I've uploaded the tarball for the latest OSELAS.Toolchain stable release.
> > It's v2012.12.1 and can be downloaded here:
> > http://www.pengutronix.de/oselas/toolchain/download/
> > 
> 
> Wouldn't it make sense to update to ptxdist 2013.01 at least for
> v2012.12.2? Reason: I always have to edit the configure script because
> of the configure check for sed on up-to-date hosts (ptxdist commit 
> http://git.pengutronix.de/?p=ptxdist.git;a=commit;h=2a89985c97422af3569eb6d268e3ccdc9c3fb0e5).

I think releasing and using ptxdist-2012.12.1 would be a better idea. Less
potential problems. Any other patches that should be in such a release?

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:[~2013-02-20 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 11:57 Michael Olbrich
2013-02-16 11:36 ` Bernhard Walle
2013-02-20 18:00   ` 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=20130220180051.GC5360@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