# Re: RFE: use patchwork to submit a patch

3 messages from 2019-10-10 to 2019-10-10. Participants: Jonathan Nieder, Eric Wong.
Thread: https://gitlist.dev/t/52016

## Jonathan Nieder, 2019-10-10 20:20

Subject: Re: RFE: use patchwork to submit a patch
Message-ID: <20191010202049.GB191800@google.com>
URL: https://gitlist.dev/e/20191010202049.GB191800%40google.com
In-Reply-To: <20191010144150.hqiosvwolm3lmzp5@chatter.i7.local>

```
(+cc: git)
Hi,

Konstantin Ryabitsev wrote[1]:

> How I envision this would work:
>
> - user creates an account (which requires a mail confirmation)
> - they choose a "submit patch" option from the menu
> - the patch submission screen has a succession of screens:

Interesting!  This reminds me a bit of https://gitgitgadget.github.io
(except using patchwork instead of github pull requests as substrate).

That leads me to wonder: should these kinds of tools share some code?
Are there any subtleties that web-to-mail patch submission interfaces
have in common or can learn from each other?

Thanks,
Jonathan

[1] https://lore.kernel.org/workflows/20191010144150.hqiosvwolm3lmzp5@chatter.i7.local/

```

## Jonathan Nieder, 2019-10-10 20:21

Subject: Re: RFE: use patchwork to submit a patch
Message-ID: <20191010202151.GC191800@google.com>
URL: https://gitlist.dev/e/20191010202151.GC191800%40google.com
In-Reply-To: <20191010200528.GA5612@dcvr>

```
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?

Thanks,
Jonathan

```

## Eric Wong, 2019-10-10 20:36

Subject: Re: RFE: use patchwork to submit a patch
Message-ID: <20191010203617.o6gyhnkjbbd7njnw@dcvr>
URL: https://gitlist.dev/e/20191010203617.o6gyhnkjbbd7njnw%40dcvr
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".

```