Re: What's cooking in git.git (Apr 2019, #02; Wed, 10)
- From
- Mazo, Andrey <amazo@checkvideo.com>
- Date
- Apr 10, 2019, 18:29 UTC
- Message-ID
- <20190410182859.20511-1-amazo@checkvideo.com>
- In-Reply-To
- <xmqqr2ab2gs6.fsf@gitster-ct.c.googlers.com>
Show 14 quoted lines
> * am/p4-branches-excludes (2019-04-02) 8 commits > - git-p4: respect excluded paths when detecting branches > - git-p4: add failing test for "git-p4: respect excluded paths when detecting branches" > - git-p4: don't exclude other files with same prefix > - git-p4: add failing test for "don't exclude other files with same prefix" > - git-p4: don't groom exclude path list on every commit > - git-p4: match branches case insensitively if configured > - git-p4: add failing test for "git-p4: match branches case insensitively if configured" > - git-p4: detect/prevent infinite loop in gitCommitByP4Change() > > "git p4" update. > > Is this ready for 'next'? >
A couple of weeks ago, Luke said he was quite busy, so I would guess, he didn't have a chance to look at these changes yet.
While we're on this, I wanted to discuss another topic. My last day at the current employer, CheckVideo, is April 19. After that, I'll lose access to amazo@checkvideo.com email address. I plan to switch to my personal email (ahippo@yandex.com) for git-p4-related discussions starting tomorrow, April 11.
Should I resend my patches from my personal address and/or add another s-o-b? Like """ Signed-off-by: Andrey Mazo <amazo@checkvideo.com> Signed-off-by: Andrey Mazo <ahippo@yandex.com> """
Also, I won't have access to a large Perforce server after April 19, which was good for testing.
-- Andrey