From: Piotr Hosowicz <piotr@hosowicz.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: GIT again
Date: Fri, 07 Jan 2011 16:13:00 +0100 [thread overview]
Message-ID: <4D272D7C.4070900@example.com> (raw)
Hello,
Sorry for bothering again. I think I fimanaged to build the kernel as I
wanted to. Lets simplify the problem. There is Linus tree and a separate
tree, which was announed here as:
git://git.kernel.org/some.git for-linus
The objective is to build the kernel with Linus sources with some.git
changes incorporatwed in it. I think I managed to achieve the objective
doing:
# let me remind myself ;-)
git clone <Linus URL here>
git remote add some git://git.kernel.org/some.git
git pull some for-linus
I've done it this way and I am convinced I've achieved the objective.
But not sure. For sure the last command modified the source, what is
what I wanted, I had to finally correct ot by hand and do git commit -a.
Am I right?
Regards,
Piotr Hosowicz
--
- Poszedłem wczoraj z żoną do ZOO
- I jak?
- Nie wzięli...
NP: Peter Green Splinter Group - Turn Your Love Away
NB: 2.6.37-20110107-1437-pztidm+
next reply other threads:[~2011-01-07 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 15:13 Piotr Hosowicz [this message]
2011-01-07 15:43 ` GIT again Michal Hocko
2011-01-07 16:07 ` Piotr Hosowicz
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=4D272D7C.4070900@example.com \
--to=piotr@hosowicz.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox