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: linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c-tools: add .gitignore
Date: Wed, 3 Aug 2016 12:02:19 +0200	[thread overview]
Message-ID: <20160803120219.2cbec11d@endymion> (raw)
In-Reply-To: <1470214547-3113-1-git-send-email-wsa@the-dreams.de>

Hi Wolfram,

On Wed,  3 Aug 2016 10:55:47 +0200, Wolfram Sang wrote:
> Don't display generated files, so 'git status' becomes useful again.

Good idea. One suggestion below.

> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
> ---
>  .gitignore       | 8 ++++++++
>  tools/.gitignore | 4 ++++
>  2 files changed, 12 insertions(+)
>  create mode 100644 .gitignore
>  create mode 100644 tools/.gitignore
> 
> diff --git a/.gitignore b/.gitignore
> new file mode 100644
> index 0000000..0d86cb6
> --- /dev/null
> +++ b/.gitignore
> @@ -0,0 +1,8 @@
> +.*
> +*.o
> +*.o.*
> +*.a
> +*.so
> +*.so.*
> +*.so.dbg
> +*.ao
> diff --git a/tools/.gitignore b/tools/.gitignore
> new file mode 100644
> index 0000000..18c268a
> --- /dev/null
> +++ b/tools/.gitignore
> @@ -0,0 +1,4 @@
> +i2cdump
> +i2cset
> +i2cget
> +i2cdetect

You could also add eeprog to eeprog/.gitignore and eeprom and eepromer
to eepromer/.gitignore.

Reviewed-by: Jean Delvare <jdelvare@suse.de>

Also a similar patch would be welcome for the 3.1 branch.

You should have write access to the repository, so I let you commit the
patches yourself?

Thanks,
-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2016-08-03 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03  8:55 [PATCH] i2c-tools: add .gitignore Wolfram Sang
2016-08-03 10:02 ` Jean Delvare [this message]
2016-08-09 20:47   ` Wolfram Sang
2016-08-03 15:22 ` Uwe Kleine-König
2016-08-09 20:42   ` 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=20160803120219.2cbec11d@endymion \
    --to=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --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).