git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David Frech" <nimblemachines@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: sharing between local "work" and "nightly build" git repos
Date: Thu, 12 Jul 2007 17:27:16 -0700	[thread overview]
Message-ID: <7154c5c60707121727k36854891u82afc4a8be822861@mail.gmail.com> (raw)
In-Reply-To: <7vmyy1rwza.fsf@assigned-by-dhcp.cox.net>

On 7/12/07, Junio C Hamano <gitster@pobox.com> wrote:
> "David Frech" <nimblemachines@gmail.com> writes:
> If you are willing to redo the nightly repository from scratch,
> I would probably recommend using --reference option when
> cloning, like this:
>
>  $ git clone --reference ~david/git git://git.kernel.org/... ~/nightly-git
>  $ cd ~/nightly-git
>  $ git checkout --track -b next origin/next
>
> Then a nightly update would go like this:
>
>  $ cd ~/nightly-git
>  $ git pull origin next
>  $ make clean
>  $ make test || barf

This makes sense, including the --track, which I neglected to set.

Could you, for my sake and the list's (if others are as confused) be
clearer about the distinctions among -l, -s, and --reference? Exactly
what they do, and their orthogonality (or lack of) really isn't clear
from reading the man page.

Thanks for your help! I'll set this up and hopefully start running it tonight.

If the build or test barfs, who should get the mail?

BTW, I figured out a sneaky way (using filters in Gmail) to send it
thru my Gmail account, so I won't have any issues with sending via
SMTP from a dynamic IP.

Cheers,

- David
-- 
If I have not seen farther, it is because I have stood in the
footsteps of giants.

  reply	other threads:[~2007-07-13  0:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 23:36 sharing between local "work" and "nightly build" git repos David Frech
2007-07-13  0:03 ` Junio C Hamano
2007-07-13  0:27   ` David Frech [this message]
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=7154c5c60707121727k36854891u82afc4a8be822861@mail.gmail.com \
    --to=nimblemachines@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).