From: "David Frech" <nimblemachines@gmail.com>
To: git@vger.kernel.org
Subject: sharing between local "work" and "nightly build" git repos
Date: Thu, 12 Jul 2007 16:36:58 -0700 [thread overview]
Message-ID: <7154c5c60707121636l585b42d4l931b08f1468ddfc@mail.gmail.com> (raw)
I'd like to have the following setup: a ~david/git directory, where I
am free to work on things, and a ~david/nightly-git, where a cron job
is going build and test a nightly "next" branch.
I'd like to share as much as possible between the two repos. My naive
first attempt was to clone the local repo (~david/git) using -l and -s
(which I admit I do not completely understand). This sort of worked,
but one issue is that doing a "git pull" in nightly is going to pull
from the *locally*-cloned repo, not from the main git. Another is that
a checkout in nightly failed with the obscure error:
[david@tashtego ~/git-nightly]% git checkout -b nightly-next next
git checkout: updating paths is incompatible with switching branches/forcing
Did you intend to checkout 'next' which can not be resolved as commit?
I assume this is because too much state is being shared the repos, and
something is unfinished in the "git" directory.
I'd love some pointers on how to:
* share as many objects as possible
* share as little state as possible
* make git pull pull from remote in both repos.
Cheers,
- David
--
If I have not seen farther, it is because I have stood in the
footsteps of giants.
next reply other threads:[~2007-07-12 23:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 23:36 David Frech [this message]
2007-07-13 0:03 ` sharing between local "work" and "nightly build" git repos Junio C Hamano
2007-07-13 0:27 ` David Frech
2007-07-13 0:33 ` David Frech
2007-07-13 5:11 ` Alex Riesen
2007-07-13 18: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=7154c5c60707121636l585b42d4l931b08f1468ddfc@mail.gmail.com \
--to=nimblemachines@gmail.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).