git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Anderson <ryan@michonline.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Question on GIT usage.
Date: Fri, 28 Oct 2005 21:43:23 -0400	[thread overview]
Message-ID: <4362D3BB.3050601@michonline.com> (raw)
In-Reply-To: <4362C700.6020901@candelatech.com>

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

Ben Greear wrote:
> 
> I have a kernel GIT tree to hold my developing patches...
> 
> I need to build this kernel for 4-5 different processors (c3, p2, p4,
> p4-smp, etc).
> 
> Is there any clever way to have this one git repository keep these
> other source trees in sync so that I can do incremental builds?
> 
> Should I perhaps have a unique git repo for each different build and
> just pull changes in from my master repo before building?
> 
> If there's a simple command to set up slave repositories like this,
> please point me to it.

There isn't, not really - but in the kernel's case, you don't need one,
either.

Build with:
	make O=/path/to/c3/tree

Put your .config in /path/to/c3/tree/

All your compiled stuff will drop into that tree, and your source tree
will stay untouched, so you can have a single GIT tree and source files.


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

  reply	other threads:[~2005-10-29  1:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29  0:49 Question on GIT usage Ben Greear
2005-10-29  1:43 ` Ryan Anderson [this message]
2005-10-29  2:06 ` Linus Torvalds
2005-10-31 23:03 ` Daniel Barkalow
2005-10-31 23:21   ` Linus Torvalds
2005-10-31 23:37     ` Daniel Barkalow
2005-10-31 23:42       ` Linus Torvalds
2005-10-31 23:56         ` Daniel Barkalow
2005-11-01  0:23         ` 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=4362D3BB.3050601@michonline.com \
    --to=ryan@michonline.com \
    --cc=git@vger.kernel.org \
    --cc=greearb@candelatech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).