Hi Göran,
I will take care of adding all the branches to gitlab next week. I will also will add my as branches as well. We can then think of merging them into main. A couple of mine are easy and safe. The macro changes for the native compilation might not be the best approach. We might want to consult an expert. I also know I have missed some cases. There are problems other fixes, we should identify them. I suspect some are buried in tickets Cheers, Mark Göran Uddeborg <goe...@uddeborg.se> writes: > Hi Mark, > > I sent my mail a couple of hours ago, so you are not that much behind! > :-) > > I've made you a maintainer in Gitlab. > > You seem more apt at migrating than I am, so I'll leave that part to > you. Take your time! > > Thank YOU! > > > Mark Diekhans skrev: > > > > Hi Göran, > > > > Sorry, I am behind on email and didn't notice this. moving > > gitlab is great. I am comfortable with either. > > > > I just sent a request access message. > > > > THANK YOU!! > > > > Moving the open issues over doesn't seem as straight forward. I > > think the way to do that might be to migrate issues from > > launchpad to github and then github to gitlab > > > > Cheers > > Mark > > > > Göran Uddeborg <goe...@uddeborg.se> writes: > > > Hi Mark and others, > > > > > > My intention also was to migrate the entire history. (Otherwise the > > > migration would have been trivial.) Do you plan to use the gitlab.com > > > repository I created? If so, do you have an account there so I can > > > give you the access rights? > > > > > > Mark Diekhans skrev: > > > > > > > > Hi Peter, > > > > > > > > My branch does not include Stefan's work and I know there are a > > > > couple of remaining problems with emacs compile. > > > > > > > > I am out of the country this week, but could work with you > > > > starting next week. I was going to convert the entire bzr tree > > > > to get the history and then merge in patches. > > > > > > > > Mark > > > > > > > > peter.julien.ray...@gmail.com <peter.julien.ray...@gmail.com> writes: > > > > > Just a quick note to say that the branch: > > > > > > > > > > > > bzr+ssh://markd-kermo...@bazaar.launchpad.net/~markd-kermodei/vm/vm-emacs-28/ > > > > > configured, made and ran out of the box under 29.3. I've not checked > > > > > the impact of Mark's other changes nor whether this includes or > > > > > obviates Stefan's cleanups but we have a potential base to work > > > > > from. If noone else steps up in a week I'll open a repo for this > > > > > version and look to integrate existing patches. A warning that if I do > > > > > this it will be github; that might stimulate others to offer to manage > > > > > on their preferred host. > > > > > Thanks again all for a wonderful tool. > > > > > regards > > > > > Peter > > > > > > > > > > > >However, I think whatever is left of the VM community needs to > > > > > >figure out if we want to breath new life into VM or let it join > > > > > >the crypt of yesterdays great software. > > > > > > > > > > > >Personally, I love VM, but the compatibility issues, as well as > > > > > >not scaling to modern email volume, is increasingly problematic. > > > > > >While I would be happy to be part of a community to resurrect > > > > > >and modernize VM, I just don't have bandwidth to be developing > > > > > >my own email client. > > > > > > > > > > > >If anyone is interested, lets start a conversation. VM is an > > > > > >amazing pieces of software. We might be able to attract others > > > > > >if we can seed a modern approach to collaborative development. > > > > > > > > > > > >Cheers > > > > > >Mark > > > > > > > > > > > >Stefan Monnier via General discussion of VM mail reader > > > > <viewmail-info@nongnu.org> writes: > > > > > >> > A naive attempt to clone from > > > > > >> > https://github.com/emacsorphanage/vm/ > > > > > >> > and run failed. I've been running a version from the bzr repo > > > > > >> > under > > > > > >> > 29.0.50. > > > > > >> > > > > > >> [ Hmm... 29.3 or the obsolete 29.0.50? ] > > > > > >> > > > > > >> > A few questions: > > > > > >> > - Am I starting from the right repo or is there a more recent > > version? > > > > > >> > - Are others running successfully in the case I'm trying? > > > > > >> > - Does any of the experienced maintainers have a sense of how > > > > > >> > hard > > this > > > > will > > > > > >> > be to fix? I'm willing to try it but would like an estimate > > > > > >> > of > > > > difficulty > > > > > >> > and time. > > > > > >> > > > > > >> Check the latest thread in this mailing-list, under the subject > > > > > >> > > > > > >> vm, emacs 28.2 (debian), urls in minibuffer > > > > > >> > > > > > >> where I sent a "cleanup" patch to help get the code closer to > > > > > >> modern > > > > > >> ELisp. John Stoffel gave up on trying to make it work, but I don't > > > > > >> think it's should be very hard. I don't use VM myself, but I'm > > > > > >> quite > > > > > >> experienced in fixing those kinds of things and would be glad to > > provide > > > > > >> guidance. Maybe you can team with John? > > > > > >> > > > > > >> > > > > > >> Stefan > > > > > >> > > > > > >> > > > > > > > > > > > > > > > > -- > > > > > Peter Rayner (he/him), Honorary Professorial Fellow, University of > > Melbourne > > > > > mobile +61 402 752 379 > > > > > zoom id 4431343191, join at > > > > <https://unimelb.zoom.us/j/4431343191?pwd=a1E5Z3JEOTRVQUJsaVdRbVUvR1QyZz09> > > > > > mail-to: peter.julien.ray...@gmail.com > > > > > google scholar: > > > > <https://scholar.google.com.au/citations?user=H3up71wAAAAJ&hl=en> > > > > > I acknowledge the Traditional Custodians of the land on which I work, > > > > > the > > > > Wurundjeri people of the Kulin nation, and pay my respect to their > > > > Elders, > > past > > > > and present > > > > > I am sending this email when convenient for me, please only respond > > > > > when > > > > convenient for you
