>>>>> "Mark" == Mark Diekhans <[email protected]> writes:
> John Stoffel <[email protected]> writes: >> 1. When I pull from https://gitlab.com/emacs-vm/vm I get the message: >> >> $ git pull >> warning: redirecting to https://gitlab.com/emacs-vm/vm.git/ >> Already up to date. > https://gitlab.com/emacs-vm/vm is the URL of the gitlab project, > the URL of the repo is: > https://gitlab.com/emacs-vm/vm.git > or if you want to use ssh: > [email protected]:emacs-vm/vm.git > that is how gitlab works. github doesn't even do the redirect from > the project page. I just originally did: git clone https://gitlab.com/emacs-vm/vm which worked, and is the URL given when I click on the 'code' button in the website. But I usually use git from the CLI, I don't run a very GUI desktop. >> 2. There's no tags for old releases, which is going to make the >> history hard to know. Is there any possibility to import the tag >> info as well? > I couldn't get fast export/import to work and end up using brz2git. > This is what it did. Then that's totally understandable! Thank you again for all your hard work. > I suspect one could find the right git commit for each tag by > writing some code to look at checksums or commit logs. This is > beyond my bandwidth to do. If there is particular tag you are > interested in, figure out where it belongs and we can add it. >> 3. Managed to pull all the branches... I wonder if we just do a big >> merge branch of all of Uday's work and see what happens? > I believe all of Uday's work that was completed is merged into > main. He was very good at managing the repo. So merging > incomplete work might break a lot of stuff. > Give there is no test suite, I think we need to exercise care. > There are also branches from other people imported, which require some > deeper investigation. > If you want to investigate some of the branches, that would be > great. >> >> Anyway, just the first observations, will be trying to play with it a >> bit and see how it works. > I am now using main with various patches merged in, including my > native-comp fixes. I know there are at least two more native-comp > problems that I worked around by loading the .el files directly. > Once I hit these, I will create tickets and try to diagnose. Ok, I'll try it out and see how it works with my IMAP/mbox setup that I use for day to day email. Ideally my problem with URLs in decoded state in the minibuffer not showing completely is fixed. Gotta go catch a plane.
