linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	linux-i2c@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH 1/2] i2c-tools: add new tool 'i2ctransfer'
Date: Wed, 22 Jun 2016 18:52:52 +0200	[thread overview]
Message-ID: <20160622185252.5ecfdf1d@endymion> (raw)
In-Reply-To: <20160621111255.1a27363e@endymion>

Hi all,

On Tue, 21 Jun 2016 11:12:55 +0200, Jean Delvare wrote:
> On Sun, 19 Jun 2016 21:56:41 +0200, Uwe Kleine-König wrote:
> > > Note, I didn't check if this patch got applied in the meantime, my
> > > excuse is that http://lm-sensors.org where AFAIK the i2c-tools repo is
> > > located isn't reachable for me.
> > 
> > This still stands. Where is the upstream repository of i2c-tools?
> 
> lm-sensors.org is dead, I am in the process of creating an i2c-tools
> repository at kernel.org. In the meantime you can use Guenter's git
> tree as a reference:
> 
> https://github.com/groeck/i2c-tools
> 
> (This is what I will use as a base for the kernel.org repository.)

This is (almost) done now. The new home of the i2c-tools repository is:

http://git.kernel.org/cgit/utils/i2c-tools/i2c-tools.git/

Guenter, Wolfram and myself have write access. As explained before, it
is based on Guenter's git mirror of the SVN repository, with the
following changes:

1* I removed the SVN tags and added clean git tags instead. SVN tags
were not so great because SVN treats tags as separate "commits" which
do not appear on the working branches. The tags I added are the parents
of the the tags I removed, they reference the same code, but in a way
that they do show up on the working branches.

2* I replaced my obsolete e-mail address by a working one for all
commits I was the author of.

When I pushed the result to kernel.org, it showed a numbers of strange
branches, maybe the result of the SVN conversion, or I messed up at
some point. I tried to clean up, please let me know if you spot
anything weird left.

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.

Wolfram, I was thinking maybe we could create
Documentation/i2c/userspace-tools with a pointer to the new repository?
Or if you have any other idea where it should be referenced? I've added
a pointer to the wiki already.

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2016-06-22 16:52 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 [this message]
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
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=20160622185252.5ecfdf1d@endymion \
    --to=jdelvare@suse.de \
    --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).