linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: "Angelo Compagnucci" <angelo.compagnucci@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-i2c@vger.kernel.org, "Guenter Roeck" <linux@roeck-us.net>
Subject: Re: New location for i2c-tools.git
Date: Mon, 4 Jul 2016 10:31:47 +0200	[thread overview]
Message-ID: <20160704103147.51185bdf@endymion> (raw)
In-Reply-To: <20160623185000.GA1611@katana>

Hi Wolfram,

On Thu, 23 Jun 2016 20:50:00 +0200, Wolfram Sang wrote:
> > 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.
> 
> Discard them, I'd say. You have all the history on your disk, so you
> have all the information from there.

For C source files, I agree, these keywords are useless.

The problem is for scripts, like decode-dimms (and sensors-detect, for
the lm-sensors part.) We can't "#include <version.h>" from these, and
my experience is that including a "manual" version string in such
scripts doesn't work because we tend to forget to update it (can
probably be addressed with some discipline.)

Also including the date turned out to be very convenient to figure out
quickly if a user report was from a recent enough version of the script
(particularly useful for sensors-detect, of which the latest snapshot
was available for direct download and in-place execution.)

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2016-07-04  8:31 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
2016-06-23 18:50                     ` Wolfram Sang
2016-07-04  8:31                       ` Jean Delvare [this message]
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=20160704103147.51185bdf@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).