From: David Woodhouse <dwmw2@infradead.org>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Clone with local alternates?
Date: Wed, 19 Apr 2006 09:39:17 +0100 [thread overview]
Message-ID: <1145435957.13200.39.camel@pmac.infradead.org> (raw)
In-Reply-To: <20060418235658.GB8915@spearce.org>
On Tue, 2006-04-18 at 19:56 -0400, Shawn Pearce wrote:
> git clone --reference=/foo git://remote/foo
That's nice. What would be even _nicer_ is if I could enforce its usage
on the server. I keep a clean copy of Linus' kernel tree on the machine
with the git dæmon, so I'd like to make it refuse to send any objects
which are in that tree and which people should already have fetched from
elsewhere anyway.
--
dwmw2
next prev parent reply other threads:[~2006-04-19 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 23:48 Clone with local alternates? David Woodhouse
2006-04-18 23:56 ` Shawn Pearce
2006-04-18 23:59 ` David Woodhouse
2006-04-19 0:19 ` [PATCH] Document git-clone --reference Shawn Pearce
2006-04-19 8:39 ` David Woodhouse [this message]
2006-04-19 9:42 ` Clone with local alternates? Eric W. Biederman
2006-04-19 9:36 ` Eric W. Biederman
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=1145435957.13200.39.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).