From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/12] Google Code: Change site
Date: Sun, 26 Jul 2015 23:34:03 +0200 [thread overview]
Message-ID: <20150726233403.7aecead1@free-electrons.com> (raw)
In-Reply-To: <1437943118-18060-1-git-send-email-maxime.hadjinlian@gmail.com>
Dear Maxime Hadjinlian,
On Sun, 26 Jul 2015 22:38:26 +0200, Maxime Hadjinlian wrote:
> Some projects have already moved on, this series bump/change the site of
> theses projects.
>
> A few are still on Google Code, they seems pretty abandonned, so a
> decision will be needed regarding theses. Switch to Alioth ? Look for a
> fork ?
With still have 1.5 years ahead of us before they go offline. So I
would suggest that we could to monitor those projects in the coming
months, and only start taking radical decision in 9-12 months.
> Maxime Hadjinlian (12):
> zxing_cpp: New package
> yaml-cpp: Bump version and change site
> libass: Bump version and change site
> explorercanvas: Bump version and change site
> libfreefare: Bump version and change site
> libiscsi: Bump version
> libllcp: Bump version and change site
> libnfc: Bump version and change site
> python-pycrc16: Change site
> python-dpkt: Bump version and change site
> python-pypcap: Bump version and change site
> qextserialport: Bump version and change site
I've applied all except the zxing_cpp patch. But I had to do some fixes
for some of them, so I'll reply to the specific patches.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-26 21:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 20:38 [Buildroot] [PATCH 00/12] Google Code: Change site Maxime Hadjinlian
2015-07-26 20:38 ` [Buildroot] [PATCH 01/12] zxing_cpp: New package Maxime Hadjinlian
2015-07-26 20:38 ` [Buildroot] [PATCH 02/12] yaml-cpp: Bump version and change site Maxime Hadjinlian
2015-07-26 20:38 ` [Buildroot] [PATCH 03/12] libass: " Maxime Hadjinlian
2015-07-26 21:34 ` Thomas Petazzoni
2015-07-26 20:38 ` [Buildroot] [PATCH 04/12] explorercanvas: " Maxime Hadjinlian
2015-07-26 21:35 ` Thomas Petazzoni
2015-07-26 20:38 ` [Buildroot] [PATCH 05/12] libfreefare: " Maxime Hadjinlian
2015-07-26 21:36 ` Thomas Petazzoni
2015-07-26 20:38 ` [Buildroot] [PATCH 06/12] libiscsi: Bump version Maxime Hadjinlian
2015-07-26 21:39 ` Thomas Petazzoni
2015-07-26 21:40 ` Maxime Hadjinlian
2015-07-27 21:38 ` Thomas Petazzoni
2015-07-27 21:50 ` Maxime Hadjinlian
2015-07-26 20:38 ` [Buildroot] [PATCH 07/12] libllcp: Bump version and change site Maxime Hadjinlian
2015-07-26 20:38 ` [Buildroot] [PATCH 08/12] libnfc: " Maxime Hadjinlian
2015-07-26 21:40 ` Thomas Petazzoni
2015-07-26 21:41 ` Thomas Petazzoni
2015-07-26 20:38 ` [Buildroot] [PATCH 09/12] python-pycrc16: Change site Maxime Hadjinlian
2015-07-26 20:38 ` [Buildroot] [PATCH 10/12] python-dpkt: Bump version and change site Maxime Hadjinlian
2015-07-26 20:38 ` [Buildroot] [PATCH 11/12] python-pypcap: " Maxime Hadjinlian
2015-07-26 21:41 ` Thomas Petazzoni
2015-07-26 20:38 ` [Buildroot] [PATCH 12/12] qextserialport: " Maxime Hadjinlian
2015-07-26 21:34 ` Thomas Petazzoni [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=20150726233403.7aecead1@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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