git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/1] add--interactive: skip index refresh in reset patch mode

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 25, 2019, 14:45 UTC
Message-ID
<nycvar.QRO.7.76.6.1911251543430.31080@tvgsbejvaqbjf.bet>
In-Reply-To
<nycvar.QRO.7.76.6.1911251523530.31080@tvgsbejvaqbjf.bet>
Hi Junio,
On Mon, 25 Nov 2019, Johannes Schindelin wrote:
Show 20 quoted lines
> On Sun, 24 Nov 2019, Junio C Hamano wrote:
>
> > "Nika Layzell via GitGitGadget" <gitgitgadget@gmail.com> writes:
> >
> > > The refresh command is called from git-add--interactive to ensure that git's
> > > view of the worktree is up-to-date. This is necessary for most commands
> > > which use git-add--interactive, as they are interacting with the worktree,
> > > however it's not necessary for git-reset, which exclusively operates on the
> > > index. This patch skips the refresh call when performing a git-reset -p,
> > > which can improve performance on large repositories which have out-of-date,
> > > or no, caches of the current worktree state.
> > >
> > > I chose to use the existing FILTER property of the flavour to make this
> > > decision. A separate REFRESH property could be added instead.
> >
> > Hmph, I wonder why this was sent my way.  How does GGG determine
> > whom to send patches to?  I, like other reviewers, prefer not to see
> > earlier rounds of patches sent directly to me unless they are about
> > areas that I am mostly responsible for (other patches I'll see them
> > and review them on the copies sent to the mailing list anyway).

Oops, I forgot to address this. The reason why this is sent your way is that you are the Git maintainer, and as such, GitGitGadget sends _all_ Git patches your way (except the Git GUI ones).

The reason for this is that this is the suggested way, as per https://git-scm.com/docs/SubmittingPatches#patch-flow:

> 5. The list forms consensus that the last round of your patch is good. Send
>    it to the maintainer and cc the list.

Ciao, Dscho

Show 28 quoted lines
> > CC'ing Dscho who has stakes in keeping the scripted "add -i" frozen,
> > while he is rewriting it in C.
>
> Thanks for pinging me!
>
> As it were, I was aware of this effort, and I am quite happy about it (and
> of course I will adjust my patch series accordingly).
>
> Thank you,
> Dscho
>
> >
> > Thanks.
> >
> > >
> > > Nika Layzell (1):
> > >   add--interactive: skip index refresh in reset patch mode
> > >
> > >  git-add--interactive.perl | 4 +++-
> > >  1 file changed, 3 insertions(+), 1 deletion(-)
> > >
> > >
> > > base-commit: 5fa0f5238b0cd46cfe7f6fa76c3f526ea98148d9
> > > Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-475%2Fmystor%2Findex-only-refresh-v1
> > > Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-475/mystor/index-only-refresh-v1
> > > Pull-Request: https://github.com/gitgitgadget/git/pull/475
> >
>
Previous: Johannes SchindelinNext: Junio C Hamano
Message 5 of 20 in “add--interactive: skip index refresh in reset patch mode”
  1. 0/1 add--interactive: skip index refresh in reset patch modeNika Layzell via GitGitGadget, Nov 23, 2019
  2. 1/1 add--interactive: skip index refresh in reset patch modeNika Layzell via GitGitGadget, Nov 23, 2019
  3. Junio C HamanoNov 24, 2019
  4. Johannes SchindelinNov 25, 2019
  5. Johannes SchindelinNov 25, 2019
  6. Junio C HamanoNov 26, 2019
  7. Cc'ing the Git maintainer on GitGitGadget contributions, was Re: [PATCH 0/1] add--interactive: skip index refresh in reset patch modeJohannes Schindelin, Jan 7, 2021
  8. Ævar Arnfjörð BjarmasonJan 7, 2021
  9. Johannes SchindelinJan 7, 2021
  10. Junio C HamanoJan 7, 2021
  11. Johannes SchindelinJan 8, 2021
  12. Junio C HamanoJan 8, 2021
  13. Johannes SchindelinJan 10, 2021
  14. Taylor BlauJan 8, 2021
  15. Johannes SchindelinJan 10, 2021
  16. Junio C HamanoJan 10, 2021
  17. Taylor BlauJan 11, 2021
  18. Junio C HamanoJan 12, 2021
  19. 胡哲宁Jan 14, 2021
  20. Junio C HamanoNov 26, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.