From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] libusbx is libusb now
Date: Tue, 15 Apr 2014 09:06:08 +0200 [thread overview]
Message-ID: <20140415070607.GA14203@omega> (raw)
In-Reply-To: <20140415070027.GA13522@omega>
Hi,
looks like I am not awake now.
On Tue, Apr 15, 2014 at 09:00:27AM +0200, Alexander Aring wrote:
> Hi,
>
> looks like we had a great timing about to switch to libusbx. Now libusbx
s/about//
> is libusb again and there is now libusbx release anymore...
>
> For more information see [0]. I think a prepare a patch to rename all
s/a prepare/I prepare/
> things to libusb again...
>
> This release name cycles makes me bad. :-(
s/bad/sad/
>
> [0] http://sourceforge.net/p/libusbx/mailman/message/31886069/
Sry, but the new libusb website wasn't updated to this information and I
didn't realize that the project is libusb again... because the
mail-archive thread from January.
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-04-15 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 7:00 [ptxdist] libusbx is libusb now... again Alexander Aring
2014-04-15 7:06 ` Alexander Aring [this message]
2014-04-15 7:25 ` [ptxdist] libusbx is libusb now Juergen Borleis
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=20140415070607.GA14203@omega \
--to=alex.aring@gmail.com \
--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