From: Stefan Beller <sbeller@google.com>
To: Jonathan Tan <jonathantanmy@google.com>
Cc: Mark Thomas <markbt@efaref.net>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Ben Peart <peartben@gmail.com>
Subject: Re: [RFC 0/4] Shallow clones with on-demand fetch
Date: Mon, 6 Mar 2017 12:01:35 -0800 [thread overview]
Message-ID: <CAGZ79kZ1K-4PJC45nSZLX3m+FrYrsz8yy__dpwmMd8niRZX_dQ@mail.gmail.com> (raw)
In-Reply-To: <c8788f30-263b-c96a-239d-940743b96b53@google.com>
On Mon, Mar 6, 2017 at 11:16 AM, Jonathan Tan <jonathantanmy@google.com> wrote:
> [1] <20170113155253.1644-1-benpeart@microsoft.com> (you can search for
> emails by Message ID in online archives like https://public-inbox.org/git if
> you don't already have them)
Not just search, but the immediate lookup is
https://public-inbox.org/git/<message-id>
so
https://public-inbox.org/git/20170113155253.1644-1-benpeart@microsoft.com
> [2] <cover.1487984670.git.jonathantanmy@google.com>
and
https://public-inbox.org/git/cover.1487984670.git.jonathantanmy@google.com
next prev parent reply other threads:[~2017-03-06 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 19:18 [RFC 0/4] Shallow clones with on-demand fetch Mark Thomas
2017-03-04 19:18 ` [RFC 1/4] upload-file: Add upload-file command Mark Thomas
2017-03-04 19:18 ` [RFC 2/4] on-demand: Fetch missing files from remote Mark Thomas
2017-03-04 19:19 ` [RFC 3/4] upload-pack: Send all commits if client requests on-demand Mark Thomas
2017-03-04 19:19 ` [RFC 4/4] clone: Request on-demand shallow clones Mark Thomas
2017-03-06 19:16 ` [RFC 0/4] Shallow clones with on-demand fetch Jonathan Tan
2017-03-06 20:01 ` Stefan Beller [this message]
2017-03-06 19:18 ` Junio C Hamano
2017-03-07 9:42 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGZ79kZ1K-4PJC45nSZLX3m+FrYrsz8yy__dpwmMd8niRZX_dQ@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=markbt@efaref.net \
--cc=peartben@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).