From: Jeff Garzik <jgarzik@pobox.com>
To: Valdis.Kletnieks@vt.edu
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Hackers Guide to git (v3)
Date: Sun, 26 Jun 2005 16:58:30 -0400 [thread overview]
Message-ID: <42BF16F6.601@pobox.com> (raw)
In-Reply-To: <200506251840.j5PIelGv012506@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Sat, 25 Jun 2005 01:13:46 EDT, Jeff Garzik said:
>
>
>>Kernel Hackers' Guide to git
>>
>>
>>1) installing git
>
>
> A nice document. Unfortunately, my brain is tiny, and there's some
> usage questions you don't cover, and I can't seem to figure out myself...
>
> Let's say I've cloned Linus's git tree, and now I want to build a kernel
> that has Linus's stuff, the 'audit' tree that's (last I checked) located at
> kernel.org/pub/scm/linux/kernel/git/dwmw2/audit-2.6, and another tree (foobar-2.6).
>
> 1) How do I do this merge?
>
> 2) How do I handle if an audit-2.6 and foobar-2.6 patch conflict -
> a) for right now...
> b) so it gets it right the *next* time I pull both and there's a collision
> (possibly between the next foobar-2.6 changeset and my modification of
> the previous changeset's results to clean the conflict)
Just 'git pull $url' all into the same repo. If git cannot auto-merge
the changes together, it will spit out a conflict for you to manually
merge. You merge just like CVS or BK: correct the code between
'<<<<<<' and '>>>>>>'.
> Another (possibly even more important to me at the moment) usage question:
>
> I have a non-git 2.6.12-mm1 tree. Given a Linus git tree and an audit-2.6 git
> tree, how do I create a tree that contains "2.6.12-mm1 plus additional
> audit-2.6 changes since Andrew cut -mm1"? (I'm chasing a bug that was
> supposedly fixed in userspace audit-0.9.10, but is still borked for me in
> 0.9.13 - I'm suspecting the bugfix is dependent on a divergence between the
> Fedora kernel (basically 2.6.12-git5 for this discussion) and -mm1...)
That's a bit tougher, since Andrew doesn't keep his stuff in git.
Jeff
prev parent reply other threads:[~2005-06-26 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-25 5:13 Kernel Hackers Guide to git (v3) Jeff Garzik
2005-06-25 9:51 ` Toufeeq Hussain
2005-06-25 18:40 ` Valdis.Kletnieks
2005-06-26 20:58 ` Jeff Garzik [this message]
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=42BF16F6.601@pobox.com \
--to=jgarzik@pobox.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@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.