From: Eric Wong <e@80x24.org>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
patchwork@lists.ozlabs.org, workflows@vger.kernel.org,
git@vger.kernel.org
Subject: Re: RFE: use patchwork to submit a patch
Date: Thu, 10 Oct 2019 20:36:17 +0000 [thread overview]
Message-ID: <20191010203617.o6gyhnkjbbd7njnw@dcvr> (raw)
In-Reply-To: <20191010202151.GC191800@google.com>
Jonathan Nieder <jrnieder@gmail.com> wrote:
> Eric Wong wrote:
> > Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
>
> >> This is actually really fast if you already have a local copy of the
> >> repository with most objects. Try this yourself if you have
> >> torvalds/linux.git locally:
> >>
> >> git clone --bare -s torvalds/linux.git test
> >
> > Yep, -s (--shared) makes cloning really cheap. One of my goals is to get
> >
> > git clone -s https://example.com/torvalds/linux.git
> >
> > and
> >
> > git clone -s https://example.com/torvalds/linux.git/clone.bundle
> >
> > working. That would make it easier for new contributors to
> > setup lightweight clones and pull in history on an as-needed
> > basis w/o hacks like shallow cloning.
>
> Does "git clone --filter=blob:none" do what you're looking for?
Oops, haven't seen that new feature :x And haven't tried, pu @
8d9027fa59b943db96a8a9090ec31d7f0f935596 is broken due to
conflicts with hashmap (probably won't have time for a bit to
look at it).
What I'm hoping to do with "git clone -s" would be client-only
and compatible with existing HTTP servers that run
"git update-server-info".
prev parent reply other threads:[~2019-10-10 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191010144150.hqiosvwolm3lmzp5@chatter.i7.local>
2019-10-10 20:20 ` RFE: use patchwork to submit a patch Jonathan Nieder
[not found] ` <20191010150729.1355f33d@coco.lan>
[not found] ` <20191010195335.fmh6atylozhehftt@chatter.i7.local>
[not found] ` <20191010200528.GA5612@dcvr>
2019-10-10 20:21 ` Jonathan Nieder
2019-10-10 20:36 ` Eric Wong [this message]
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=20191010203617.o6gyhnkjbbd7njnw@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=mchehab+samsung@kernel.org \
--cc=patchwork@lists.ozlabs.org \
--cc=workflows@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.
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).