From: Sverre Rabbelier <srabbelier@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Nicolas Pitre <nico@cam.org>,
Julian Phillips <julian@quantumfyre.co.uk>,
Daniel Barkalow <barkalow@iabervon.org>,
Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: [PATCH] fix simple deepening of a repo
Date: Mon, 24 Aug 2009 22:00:39 -0700 [thread overview]
Message-ID: <fabb9a1e0908242200v22057a72ta4998633701c408b@mail.gmail.com> (raw)
In-Reply-To: <20090825021223.GE1033@spearce.org>
Heya,
On Mon, Aug 24, 2009 at 19:12, Shawn O. Pearce<spearce@spearce.org> wrote:
> git fetch --uploadpack='git upload-pack --ref refs/changes/88/4488/2' URL refs/changes/88/4488/2
>
> Personally I'd prefer extending the protocol, because making the
> end user supply information twice is stupid.
$ git fetch --unadvertised URL refs/changes/88/4488/2
And we expand that to the above behind the screens?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-08-25 5:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 5:52 git fetch --depth=* broken? Nicolas Pitre
2009-08-24 4:04 ` [PATCH] fix simple deepening of a repo Nicolas Pitre
2009-08-24 4:49 ` Junio C Hamano
2009-08-24 13:55 ` Nicolas Pitre
2009-08-24 14:20 ` Johan Herland
2009-08-24 22:21 ` Junio C Hamano
2009-08-24 16:26 ` Daniel Barkalow
2009-08-24 22:30 ` Julian Phillips
2009-08-25 0:18 ` Nicolas Pitre
2009-08-25 2:12 ` Shawn O. Pearce
2009-08-25 5:00 ` Sverre Rabbelier [this message]
2009-08-25 5:21 ` Junio C Hamano
2009-08-25 6:12 ` Shawn O. Pearce
2009-08-25 6:33 ` Junio C Hamano
2009-08-25 15:14 ` Shawn O. Pearce
2009-08-26 2:10 ` Shawn O. Pearce
2009-08-26 7:08 ` Johannes Sixt
2009-08-26 8:22 ` Shawn O. Pearce
2009-08-26 9:03 ` Junio C Hamano
2009-08-26 17:03 ` Shawn O. Pearce
2009-08-28 17:30 ` [RFC PATCH] upload-pack: expand capability advertises additional refs Shawn O. Pearce
2009-08-28 19:07 ` 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=fabb9a1e0908242200v22057a72ta4998633701c408b@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=julian@quantumfyre.co.uk \
--cc=nico@cam.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).