From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] sensors-detect: Add support for NCT6775F
Date: Wed, 07 Jul 2010 19:32:21 +0000 [thread overview]
Message-ID: <20100707213221.28451ad0@hyperion.delvare> (raw)
In-Reply-To: <20100706222437.GA31051@ericsson.com>
On Wed, 7 Jul 2010 09:03:04 -0700, Guenter Roeck wrote:
> On Wed, Jul 07, 2010 at 11:53:27AM -0400, Jean Delvare wrote:
> > On Wed, 7 Jul 2010 08:29:55 -0700, Guenter Roeck wrote:
> > > On Wed, Jul 07, 2010 at 07:40:57AM -0400, Jean Delvare wrote:
> > > > Looks all sane, thanks for doing this. Shall I commit it, or should I
> > > > create a developer account and let you commit it? You already have an
> > > > account for the wiki, letting you commit to the repository is only one
> > > > configuration line away. So it's as you prefer.
> > >
> > > I really prefer the git way of doing things, meaning I prefer to have someone
> > > else have a close look at my code, and not commit my own junk myself.
> > > I also never worked with svn before, so I would be a bit concerned about
> > > screwing up the repository. Not really a good idea to make my first svn commit
> > > into a public repository.
> >
> > SVN is really easy. It's almost the same as CVS if you've used CVS
> > before. And it's definitely easier than git.
> >
> Easier than git - really ? After having worked with git for several years,
> I am still amazed (or, rather, I am more and more amazed) how easy and fast
> things are with git. Granted, one problem is that it is also very easy
> to screw up, which makes it very difficult to use with junior engineers ...
It is indeed very easy to screw up with git. It is also easy to put
your local repository in a state from which you don't know to recover.
It isn't surprising anyway, as git is much more powerful than SVN (let
alone CVS). With greater power comes greater ways to mess everything up.
Anyway, enough of this, I really don't have the time to discuss the
merits of git vs SVN, others have done it already. The only thing I
keep in mind is that you would have been more likely to contribute
directly if we were using git. If a lot of other developers start
claiming the same, then who knows...
> > > So let's keep it as is for now, and go ahead and commit. We can revisit that
> > > when you get tired having to deal with my patches.
> >
> > I'm tired already ;)
> >
> > Just joking. I'll be glad to review and commit your patches if such is
> > your desire.
>
> Let's at least stick with it for now.
I've just applied your patch, thanks for your contribution.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2010-07-07 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 22:24 [lm-sensors] [PATCH] sensors-detect: Add support for NCT6775F and Guenter Roeck
2010-07-07 11:40 ` [lm-sensors] [PATCH] sensors-detect: Add support for NCT6775F Jean Delvare
2010-07-07 15:53 ` Jean Delvare
2010-07-07 16:03 ` Guenter Roeck
2010-07-07 19:32 ` Jean Delvare [this message]
2010-07-08 20:15 ` [lm-sensors] [PATCH] sensors-detect: Add support for several JC42.4 Guenter Roeck
2010-07-09 9:15 ` [lm-sensors] [PATCH] sensors-detect: Add support for several Jean Delvare
2010-09-08 15:35 ` [lm-sensors] [PATCH] sensors-detect: Add support for max6695/96 Guenter Roeck
2010-09-08 19:06 ` Jean Delvare
2010-09-08 19:39 ` Guenter Roeck
2011-06-26 20:38 ` [lm-sensors] [PATCH] sensors-detect: Add support for NXP/Philips Guenter Roeck
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=20100707213221.28451ad0@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.