Re: [PATCH v2 00/14] Improve git-status --ignored
Karsten Blees writes: > I'll send fixups for #11 and #14, or you can pick the entire series rebased > to pu from: > https://github.com/kblees/git/tree/kb/improve-git-status-ignored-v2-pu > git pull git://github.com/kblees/git.git kb/improve-git-status-ignored-v2-pu Will take a look; very much appreciated. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 00/14] Improve git-status --ignored
Am 15.04.2013 22:25, schrieb Junio C Hamano: > Karsten Blees writes: > >> Am 15.04.2013 21:33, schrieb Junio C Hamano: >>> Junio C Hamano writes: >>> Karsten Blees writes: > This patch series addresses several bugs and performance issues in > .gitignore processing. A 8-patch series ending at 5d765dc7888b (dir.c: git-status: avoid is_excluded checks for tracked files, 2013-03-18) has been cooking in 'next'; in general we won't revert and requeue a new round for a topic that has already merged to 'next'. >> >> I'm sorry to have caused such trouble. I thought you were expecting a reroll >> from this: > > Heh, that was an ancient history. My git time is scarce, so progress is slow...guess I need some performance improvements, too :-) > > It is not such a big deal to revert stuff from 'next'. I've tried > to queue this reroll, but tentatively ejected the result from 'pu' > for today's integration run, as as/check-ignore topic has an > unpleasant conflict with this. > I'll send fixups for #11 and #14, or you can pick the entire series rebased to pu from: https://github.com/kblees/git/tree/kb/improve-git-status-ignored-v2-pu git pull git://github.com/kblees/git.git kb/improve-git-status-ignored-v2-pu HTH, Karsten -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 00/14] Improve git-status --ignored
Karsten Blees writes: > Am 15.04.2013 21:33, schrieb Junio C Hamano: >> Junio C Hamano writes: >> >>> Karsten Blees writes: >>> This patch series addresses several bugs and performance issues in .gitignore processing. >>> >>> A 8-patch series ending at 5d765dc7888b (dir.c: git-status: avoid >>> is_excluded checks for tracked files, 2013-03-18) has been cooking >>> in 'next'; in general we won't revert and requeue a new round for a >>> topic that has already merged to 'next'. >>> > > I'm sorry to have caused such trouble. I thought you were expecting a reroll > from this: Heh, that was an ancient history. It is not such a big deal to revert stuff from 'next'. I've tried to queue this reroll, but tentatively ejected the result from 'pu' for today's integration run, as as/check-ignore topic has an unpleasant conflict with this. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 00/14] Improve git-status --ignored
Am 15.04.2013 21:33, schrieb Junio C Hamano: > Junio C Hamano writes: > >> Karsten Blees writes: >> >>> This patch series addresses several bugs and performance issues in >>> .gitignore processing. >> >> A 8-patch series ending at 5d765dc7888b (dir.c: git-status: avoid >> is_excluded checks for tracked files, 2013-03-18) has been cooking >> in 'next'; in general we won't revert and requeue a new round for a >> topic that has already merged to 'next'. >> I'm sorry to have caused such trouble. I thought you were expecting a reroll from this: Am 19.03.2013 15:48, schrieb Junio C Hamano: > Would we we better off kicking nd/read-directory-recursive-optim > back to 'pu' (and eventually ejecting it) and replacing it with a > reroll of Karsten's series when it comes, perhaps? >> Is this "v2" an update for that topic? > > Hmph, it seems to be the case. I was hoping that the one in 'next' > was basically in a good shape, not so broken to require a wholesale > replacement like this. Overall, this round of reroll seems to be > better structured. > > Let's revert the v1 from 'next', queue this one to 'pu', and make it > advance slooowly this time. > Thanks. I don't plan any more rerolls unless required by upcoming discussion. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 00/14] Improve git-status --ignored
Junio C Hamano writes: > Karsten Blees writes: > >> This patch series addresses several bugs and performance issues in >> .gitignore processing. > > A 8-patch series ending at 5d765dc7888b (dir.c: git-status: avoid > is_excluded checks for tracked files, 2013-03-18) has been cooking > in 'next'; in general we won't revert and requeue a new round for a > topic that has already merged to 'next'. > > Is this "v2" an update for that topic? Hmph, it seems to be the case. I was hoping that the one in 'next' was basically in a good shape, not so broken to require a wholesale replacement like this. Overall, this round of reroll seems to be better structured. Let's revert the v1 from 'next', queue this one to 'pu', and make it advance slooowly this time. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 00/14] Improve git-status --ignored
Karsten Blees writes: > This patch series addresses several bugs and performance issues in > .gitignore processing. A 8-patch series ending at 5d765dc7888b (dir.c: git-status: avoid is_excluded checks for tracked files, 2013-03-18) has been cooking in 'next'; in general we won't revert and requeue a new round for a topic that has already merged to 'next'. Is this "v2" an update for that topic? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
