From: Jean Delvare <jdelvare@suse.de>
To: Angelo Compagnucci <angelo.compagnucci@gmail.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Wolfram Sang" <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org, "Guenter Roeck" <linux@roeck-us.net>
Subject: Re: New location for i2c-tools.git
Date: Thu, 23 Jun 2016 19:40:16 +0200 [thread overview]
Message-ID: <20160623194016.6d89dc01@endymion> (raw)
In-Reply-To: <CA+TH9VkXPFBgAiLHwx+_B96RRYMmtG-Kc_5qN-0Ps6FceBrVhg@mail.gmail.com>
On Thu, 23 Jun 2016 12:36:38 +0200, Angelo Compagnucci wrote:
> 2016-06-23 11:53 GMT+02:00 Jean Delvare <jdelvare@suse.de>:
> > Hi Angelo,
> >
> > On Thu, 23 Jun 2016 09:57:49 +0200, Angelo Compagnucci wrote:
> >> 2016-06-23 9:32 GMT+02:00 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
> >> > Hello,
> >> >
> >> > mainly for the archives I reply with an updated Subject.
> >> >
> >> > On Wed, Jun 22, 2016 at 06:52:52PM +0200, Jean Delvare wrote:
> >> >> The new home of the i2c-tools repository is:
> >> >>
> >> >> http://git.kernel.org/cgit/utils/i2c-tools/i2c-tools.git/
> >>
> >> This repository presents something strange, the tagged release 3.1.2
> >> of some months ago is no more.
> >>
> >> This is quite awful cause some distributions (ex: buildroot ) used
> >> that tag as the latest released version and now they are broken.
> >>
> >> Can anyone fix this?
> >
> > Quoting myself from yesterday in this very thread:
> >
> > "We are almost there, except that a few commits went to the
> > i2c-tools-3.1 branch AFTER Guenter mirrored it for the last time, so
> > they are missing from the git tree. I will extract them from my local
> > copy tomorrow and commit them."
> >
> > Yesterday's tomorrow is today.
>
> Sorry for the noise, I totally missed that conversation. A big thank you!
Everything should be there now.
The only remaining problem is that some files have occurrences of $Id$,
$Revision$ and $Date$, which SVN would replace on the fly but git does
not. Not sure what to do with them, replace them with something git
supports (not sure that exists?), or discard them.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2016-06-23 17:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 10:40 [PATCH 0/2] new tool 'i2ctransfer' Wolfram Sang
2015-06-19 10:40 ` [PATCH 1/2] i2c-tools: add " Wolfram Sang
[not found] ` <1434710432-4182-2-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-09-11 8:42 ` Jean Delvare
2016-02-14 19:08 ` Wolfram Sang
2016-04-27 17:33 ` Uwe Kleine-König
2016-04-27 17:37 ` Wolfram Sang
2016-06-19 19:56 ` Uwe Kleine-König
2016-06-19 20:00 ` Wolfram Sang
2016-06-19 21:51 ` Uwe Kleine-König
2016-06-20 6:08 ` Wolfram Sang
2016-06-20 6:49 ` Uwe Kleine-König
2016-06-21 9:12 ` Jean Delvare
2016-06-22 16:52 ` Jean Delvare
2016-06-22 20:40 ` Guenter Roeck
2016-06-22 22:18 ` Wolfram Sang
2016-06-23 7:32 ` New location for i2c-tools.git Uwe Kleine-König
2016-06-23 7:57 ` Angelo Compagnucci
2016-06-23 9:53 ` Jean Delvare
2016-06-23 10:36 ` Angelo Compagnucci
2016-06-23 17:40 ` Jean Delvare [this message]
2016-06-23 18:50 ` Wolfram Sang
2016-07-04 8:31 ` Jean Delvare
2016-07-04 14:38 ` Wolfram Sang
2015-06-19 10:40 ` [PATCH 2/2] i2c-tools: i2ctransfer: clean up allocated resources Wolfram Sang
2015-09-11 9:12 ` Jean Delvare
2016-02-14 19:20 ` Wolfram Sang
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=20160623194016.6d89dc01@endymion \
--to=jdelvare@suse.de \
--cc=angelo.compagnucci@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).