Hi

I'm proposing starting fresh meaning initially no history in github. You'd need 
to jump back to Source Forge for the older changes. They would not be lost. 
We'd freeze Source Forge and add a link to them. Part of the reason for doing 
this is that there is a bunch of old stuff in Source Forge and this way we 
don't need to worry about cleaning it up or pulling in stuff we don't want. So, 
we are good for the history - it's just a side step to access Source Forge.

With this proposal, in github, we'd see

   matlab.el      "initial commit"
   etc.

  And then on the page:

  History
  matlab-mode has a history dating back many years. Older contributions can be 
found in https://sourceforge.net/projects/matlab-emacs/.

If you feel like we should import the history, could you help with that? Maybe 
the easiest way would be to just copy the history from the main branch, then 
people with other branches could choose to create new forks in github with 
their changes.

Regardless, we should keep the Source Forge reference in the github repo.

Thanks
John


________________________________
From: Uwe Brauer
Sent: Monday, July 29, 2024 1:20 PM
To: John Ciolfi
Cc: Uwe Brauer; matlab-emacs-discuss@lists.sourceforge.net; Nidish Narayanaa 
Balaji
Subject: Re: Move of matlab-mode from Source Forge to github

>>> "JC" == John Ciolfi <cio...@mathworks.com> writes:

> Hi
> I haven't spent time looking into how to make the branch 'default'
> (too many other items on my plate).

I did this in the past, without problems, I am just retrying it again
and tell you the details later.

> Once that's done, I can upload the repo to github.
I am not sure what you mean by upload.


> My original proposal was to start fresh in github and keep the older
> history in Source Forge as this is simpler. Is that okay?


Ah wait, I am confused. That defies a bit the idea of a version control
system, doesn't it?

I mean I understand that you are not interested in very old versions, that
is why I proposed some cleanup, rebase and deleting old branches.

But, please note, that our repository is about 5 MB even less. For
example GNU emacs, goes way back at least to 1995 (using RCS), and well
it is about 1GB. But I can see the benefits of having a long history.

Another problem are the branches that are yet not even merged. Do you
want to delete and forget them?

Uwe


> thanks
> John

> ________________________________
> From: Uwe Brauer
> Sent: Monday, July 29, 2024 11:21 AM
> To: John Ciolfi
> Cc: Uwe Brauer; matlab-emacs-discuss@lists.sourceforge.net; Nidish Narayanaa 
> Balaji
> Subject: Re: Move of matlab-mode from Source Forge to github

>>> "JC" == John Ciolfi <cio...@mathworks.com> writes:

>> Okay, I'll look into seeing if we can call it default.
> Any news?

> I also would like before we move

>     1. Do some rebasing and make the graph a bit leaner

>     2. Delete some very old branches which are merged into master a long time 
> ago.

>     3. That most likely will imply that everybody should then clone
> again once we move to github, since I am not sure that the rebasing
> and deleting branches will not break things.

> Uwe


>> ________________________________
>> From: Uwe Brauer
>> Sent: Wednesday, July 17, 2024 2:32 PM
>> To: John Ciolfi
>> Cc: Uwe Brauer; matlab-emacs-discuss@lists.sourceforge.net; Nidish Narayanaa 
>> Balaji
>> Subject: Re: Move of matlab-mode from Source Forge to github

>>> "JC" == John Ciolfi <cio...@mathworks.com> writes:

>> Hi

>>> Hi
>>> For the main branch, the convention is to use "main" in github. I'm
>>> not sure if there's a way to switch from that. If possible, I'd like
>>> to use that. Here's an example of a MathWorks sponsored project,
>>> https://github.com/mathworks/MATLAB-language-server.

>> Ah, well, this is true for repositories you start on github/gitlab etc 
>> nowadays.


>> Some remarks

>> 1. In git you can rename branches easily (while in mercurial you
>> would need the evolve extension, and even then it is more
>> complicated). Historically the «main» branch was called «master».
>> But on political reasons «main» is now preferred.

>> 2. As I said we push an existing repository, that is different from
>> creating an empty one in github. For me using the name «default»
>> would simplify things considerably especially now, since I had to
>> upgrade my Ubuntu system and the most recent mercurial version is
>> less flexible concerning the hg-git exporter.

>> 3. So I propose we start with default, if we see that a lot of
>> people want to contribute and are confused by this name, we might
>> reconsider (this also gives me time to look for a technical
>> solution)

>> Uwe

--
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military.
I support the EU and NATO membership of Ukraine.

_______________________________________________
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

Reply via email to