From: Ben Greear <greearb@candelatech.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Question on GIT usage.
Date: Fri, 28 Oct 2005 17:49:04 -0700 [thread overview]
Message-ID: <4362C700.6020901@candelatech.com> (raw)
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.
Thanks!
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2005-10-29 0:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 0:49 Ben Greear [this message]
2005-10-29 1:43 ` Question on GIT usage Ryan Anderson
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=4362C700.6020901@candelatech.com \
--to=greearb@candelatech.com \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).