Re: git guidance

[Tilman Schmidt <tilman@imap.cc>]

[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]

Willy,

thanks for your kind answer.

Am Mi 28 Nov 2007 00:52:38 +0100, Willy Tarreau schrieb:
> Tilman, there was a howto by Jeff Garzik I believe.

Yes, I started from that and it's fine as far as it goes. The
"Everyday GIT With 20 Commands Or So" document was quite helpful
too, especially the section "Individual Developer (Participant)".
But they don't quite cover my workflow yet.

> 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 think I got that part. My questions concern practical things
like when to make a new branch, how to resubmit a patch following
post-commit changes, what to do when "git format-patch" doesn't
produce the desired result or when "git pull" obstinately declares
"Already up-to-date" even though I know that isn't true, how to
track a patch after submission to LKML to see when or whether it
appears in the main tree, or how to scrub the history to stop
"git log origin..HEAD" from listing (and "git format-patch" from
formatting) long-merged changes as new. Well, I'll take that up on
the git@vger.kernel.org list then, as proposed by J. Bruce Fields,
in order not to annoy LKML readers any longer.

> 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.

That's what I'm thinking. What I'm trying to do can't be that
different from what all those happy git users are doing. I guess
if I could just watch an experienced git user at work for a day
most of my problems would vanish.

Thanks,
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@imap.cc
Bonn, Germany
Yes, I have searched Google!


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]