From: Jeff Garzik <jgarzik@pobox.com>
To: Mike McCormack <mike@codeweavers.com>
Cc: git@vger.kernel.org
Subject: Re: Wine + GIT
Date: Mon, 05 Dec 2005 21:03:31 -0500 [thread overview]
Message-ID: <4394F173.6000505@pobox.com> (raw)
In-Reply-To: <4394CD68.8020500@codeweavers.com>
Mike McCormack wrote:
> Hi All,
>
> The Wine project has started maintaining a wine.git in parallel to the
> Wine CVS. To introduce Wine developers to GIT, we've put together a
> short introduction on the Wine Wiki on using GIT to maintain patches.
> You can find it at:
> http://wiki.winehq.org/GitWine
Very cool! :)
Comments:
1) I wrote a git howto for kernel hackers, 95% of which applies to other
projects as well: http://linux.yyz.us/git-howto.html
2) The "git-foo" commands are apparently uncool. "git foo ..." is
preferred.
3) replace
git-diff-index -p HEAD
with
git diff HEAD
4) "git commit -a" can often replace git-update-index+git-commit
5) never ever do
git-checkout -f HEAD
HEAD should always be a symlink. 'git checkout -f master' is probably
what you want.
6) For merges with hand-merged conflicts, I could have sworn that either
a "git commit -a" or 'git-update-index' + 'git commit' was required.
Maybe I'm wrong, or that has changed?
next prev parent reply other threads:[~2005-12-06 2:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 23:29 Wine + GIT Mike McCormack
2005-12-06 2:03 ` Jeff Garzik [this message]
2005-12-06 2:26 ` Junio C Hamano
2005-12-06 17:08 ` J. Bruce Fields
2005-12-06 17:33 ` Junio C Hamano
2005-12-06 17:39 ` J. Bruce Fields
2005-12-06 17:53 ` Jon Loeliger
2005-12-06 21:22 ` git shorthands (was: Re: Wine + GIT) Andreas Ericsson
2005-12-07 0:56 ` Wine + GIT Ben Clifford
2005-12-06 19:01 ` Jeff Garzik
2005-12-06 19:06 ` Mike McCormack
2005-12-06 2:18 ` Jeff Garzik
2005-12-06 23:08 ` Nick Hengeveld
2005-12-06 23:27 ` Andreas Ericsson
2005-12-06 9:02 ` Marco Costalba
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 7:30 linux
2005-12-08 9:29 ` Fredrik Kuivinen
2005-12-08 18:17 ` Junio C Hamano
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=4394F173.6000505@pobox.com \
--to=jgarzik@pobox.com \
--cc=git@vger.kernel.org \
--cc=mike@codeweavers.com \
/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.