Re: Progress on merging Eglot?

["João Távora" <joaotavora@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1875 bytes --]

[Sorry, I took part of this conversation off-list by mistake.  Bringing it
back.]

On Thu, Sep 8, 2022 at 3:53 PM Payas Relekar <relekarpayas@gmail.com> wrote:

> João Távora <joaotavora@gmail.com> writes:
> > On Thu, Sep 8, 2022 at 3:25 PM Payas Relekar <relekarpayas@gmail.com>
> wrote:
> >
> > If we choose to recreate commit history one time, can we simply replace
> >> the #num with Github issue link? Should be relatively simple regex find
> >> and replace.
> >>
> >
> > I think so too. If you'd like to work on these scripts, test them, and
> put
> > the result somewhere we
> > can inspect them, it'd be very appreciated.
>
> Sure. I'm not much versed on Git side of things, but I'll give it a try
> over weekend. At the very least, creating commit messages shouldn't be
> much trouble.
>

Cool, I'll put you down for item 2 then!  I recommend the tool
https://github.com/newren/git-filter-repo.  Here's an example of how it's
used.

https://stackoverflow.com/questions/60863773/git-bulk-change-of-commit-dates

This tool seems to be preferred over `git filter-branch` nowadays and is
easy to
combine with whatever scripting language you're comfortable with.

I've used one of the two in the past (can't remember which).  There are
others, so choose your poison. I also vaguely  remember that running the
script on windows was about a million times slower than on a GNU/linux
box.
Also not sure if that holds anymore.

So the inputs should be Eglot's main repo (master branch) and some branch
of the emacs.git repo.  The output should be something like a new
lisp/progmodes/eglot.el added and then some 900+ commits on top of it.
Place this on a git branch somewhere so we can look at it.

We'll probably need to make adjustments, so make sure to post the script
somewhere with instructions on how to use it.

João

[-- Attachment #2: Type: text/html, Size: 2966 bytes --]