From: Willy Tarreau <w@1wt.eu>
To: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Cc: Tilman Schmidt <tilman@imap.cc>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: git guidance
Date: Wed, 28 Nov 2007 00:52:38 +0100 [thread overview]
Message-ID: <20071127235237.GF15227@1wt.eu> (raw)
In-Reply-To: <20071127235511.bd9557f0.Kristoffer.ericson@gmail.com>
On Tue, Nov 27, 2007 at 11:55:11PM +0100, Kristoffer Ericson wrote:
> Greetings,
>
> Google is your friend. If you're looking for irc channels you can always try #git at irc.freenode.net
> Git howto/tutorial/... doesn't belong in the kernel mailinglist.
Well, I don't agree with you. His question is about how to use GIT to
develop his driver.
1) linux-kernel is a development ML.
2) he needs help from people how already encountered such beginner's
issues and who might git very good advices.
It should not turn into an endless thread led by people who want to
redefine GIT's roadmap, but experience sharing helps a lot with GIT.
Tilman, there was a howto by Jeff Garzik I believe. It helped me
a lot when I didn't understand a damn command, even if it was in
the very old ages (version 0.5 or something like this). The tutorials
on the GIT site are quite good too. You must read them entirely and
proceed with the examples as you read them. Believe me, it helps you
understand a lot of things, specially about the split in 3 parts
(objects, cache, and working dir).
I really think that if your patches do not apply, it's because you
have lost some changes due to a wrong initial use possibly caused
by a mis-understanding of the tool. It happened to me too, but in
this case you can almost certainly find your old changes in older
commits.
I really hope that soon someone will come up with a big 400-pages
book called "GIT" with a lot of good advices. It would be awesome.
Anyway, don't get demotivated about the tool or the workflow. If
you find it inconvenient to use, you're doing something wrong and
you don't know it.
Regards,
Willy
next prev parent reply other threads:[~2007-11-27 23:52 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 22:33 git guidance Tilman Schmidt
2007-11-27 22:54 ` J. Bruce Fields
2007-11-27 22:55 ` Kristoffer Ericson
2007-11-27 23:52 ` Willy Tarreau [this message]
2007-11-28 0:43 ` Kristoffer Ericson
2007-11-28 0:49 ` Randy Dunlap
2007-11-28 12:49 ` Al Boldi
2007-11-28 13:45 ` Rogan Dawes
[not found] ` <Pine.LNX.4.64.0711281545170.27959@racer.site>
2007-11-28 17:14 ` Al Boldi
2007-11-28 18:14 ` Johannes Schindelin
2007-11-28 18:30 ` Al Boldi
2007-11-28 18:41 ` Jakub Narebski
2007-11-29 5:27 ` Al Boldi
2007-11-29 12:57 ` Kyle Moffett
2007-11-28 13:38 ` Tilman Schmidt
2007-11-28 21:20 ` Willy Tarreau
2007-11-28 11:23 ` Tilman Schmidt
2007-11-28 12:31 ` Kristoffer Ericson
2007-11-27 23:20 ` Jan Engelhardt
2007-11-28 15:15 ` Dave Quigley
2007-11-28 15:57 ` Tilman Schmidt
2007-11-28 16:37 ` Dave Quigley
2007-11-28 19:10 ` willem
2007-11-28 19:18 ` Dave Quigley
2007-11-28 23:22 ` Haavard Skinnemoen
2007-11-29 12:45 ` Tilman Schmidt
2007-11-29 13:03 ` Haavard Skinnemoen
2007-11-28 7:41 ` Arkadiusz Miskiewicz
2007-11-29 12:51 ` Tilman Schmidt
-- strict thread matches above, loose matches on Subject: below --
2007-11-29 15:52 Jing Xue
2007-11-29 16:19 ` Linus Torvalds
2007-12-01 6:50 ` Al Boldi
2007-12-04 22:21 ` Phillip Susi
2007-12-07 17:35 ` Al Boldi
2007-12-06 18:24 ` Andreas Ericsson
2007-12-07 18:55 ` Al Boldi
2007-12-06 20:22 ` Johannes Schindelin
2007-12-07 4:37 ` Al Boldi
2007-12-07 8:40 ` Andreas Ericsson
2007-12-07 10:53 ` Al Boldi
2007-12-07 11:47 ` Jakub Narebski
2007-12-07 19:04 ` Al Boldi
2007-12-07 19:36 ` Valdis.Kletnieks
2007-12-07 22:07 ` Luke Lu
2007-12-08 4:56 ` Al Boldi
2007-12-08 5:16 ` Valdis.Kletnieks
2007-12-08 10:41 ` Al Boldi
2007-12-08 11:13 ` Johannes Schindelin
2007-12-07 12:30 ` Andreas Ericsson
2007-12-07 21:17 ` david
2007-12-07 22:00 ` Björn Steinbrink
2007-12-06 21:46 ` Phillip Susi
2007-12-08 6:33 ` Martin Langhoff
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=20071127235237.GF15227@1wt.eu \
--to=w@1wt.eu \
--cc=kristoffer.ericson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
/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