GitGitGadget and `next`, was Re: [PATCH v5 3/3] ls-files.c: add --deduplicate option

Hi Junio,

I just noticed that this still waited in my inbox for me to answer it.

On Fri, 22 Jan 2021, Junio C Hamano wrote:

Just being curious, but when a series hits 'next', would the way in
which the user interacts with GGG change?

My hunch is that we should probably tell new users (for who GitGitGadget
now uses the "new user" PR label) about the expectations of only adding
patches on top (i.e. in a new PR), unless the branch gets kicked out of
`next`.

With or without GGG, what is done on the local side is not all that
different---you build new commits on top without disturbing the commits
that are in 'next'. Then what?  Push it again (this time there is no
need to force) and submit the additional ones via `/submit`?

GitGitGadget would send the entire patch series, which is probably not a
good idea.

Ciao,
Dscho