Re: Git in Outreachy?
- From
Elijah Newren <newren@gmail.com>
- Date
- Sep 17, 2020, 15:34 UTC
- Message-ID
- <CABPp-BHV5-UUio69b1ZnwuRwyj66HUEy3A24wvxELorR_1FB=g@mail.gmail.com>
- In-Reply-To
- <CAP8UFD1n_PYzygFCgNDt3T=EQhbcuaTYFCfNN5n45OHRh45KOg@mail.gmail.com>
On Thu, Sep 17, 2020 at 2:47 AM Christian Couder <christian.couder@gmail.com> wrote:
Show 23 quoted lines
> > On Wed, Sep 16, 2020 at 11:01 AM Christian Couder > <christian.couder@gmail.com> wrote: > > > On Wed, Sep 2, 2020 at 10:50 AM Johannes Schindelin > > <Johannes.Schindelin@gmx.de> wrote: > > > > > As to projects, I would like to believe that > > > https://github.com/gitgitgadget/git/issues has grown into a useful > > > resource. > > > > Thanks for the useful resource! > > > > I would be interested in mentoring, or better co-mentoring, the > > following projects: > > > > - Accelerate rename detection and range-diff > > (https://github.com/gitgitgadget/git/issues/519): ideally I would > > co-mentor with someone a bit familiar with the suggested algorithms. > > Proposed on Outreachy's website: > > https://www.outreachy.org/outreachy-december-2020-internship-round/communities/git/accelerate-rename-detection-and-the-range-diff-com/cfp/
As a heads up, I'm going to be sending many patches modifying quite a wide range of diffcore-rename.c in the coming months for accelerating rename detection. Maybe I'll get them all upstreamed before outreachy starts, but that's not so clear. As I mentioned in the gitgitgadget issue, the ideas outlined there and the methods I implemented are different and complementary, but there is a pretty large risk of conflicts we need to resolve if I don't finish landing all my patches first.
Show 9 quoted lines
> > > - Add support for drop!/reword! commits to `git rebase -i` > > (https://github.com/gitgitgadget/git/issues/259, > > https://public-inbox.org/git/alpine.DEB.2.21.1.1710151754070.40514@virtualbox/) > > - Invent a way to retain reflogs for a while after the ref was deleted > > (https://github.com/gitgitgadget/git/issues/236): I guess this might > > be implemented as part of the new `git maintenance` builtin. > > I will also likely submit a proposal for one of the above projects.