Discussion:
[Texmacs-dev] Multiple "git svn" mirrors of texmacs on github, problems...?
sadhen
2018-06-20 12:27:43 UTC
Permalink
Just create a new repo:


https://github.com/texmacs/GNUTeXmacs


PRs on any of the repos are welcome.


原始邮件
发件人:Zhaocong ***@gmail.com
收件人:Darcy ***@zoho.com
发送时闎:2017幎10月13日(呚五) 19:34
䞻题:Re: [Texmacs-dev] Multiple "git svn" mirrors of texmacs on github, problems...?


Darcy Shen, in your repo, the toplevel directory contains misc/ src/ web/ I think we should only contains the src/ directory. misc/ and web/ are probably out of date and they are not "source code".
ederag
2018-06-20 16:04:41 UTC
Permalink
Post by sadhen
https://github.com/texmacs/GNUTeXmacs
PRs on any of the repos are welcome.
原始邮件
发送时间:2017年10月13日(周五) 19:34
主题:Re: [Texmacs-dev] Multiple "git svn" mirrors of texmacs on github, problems...?
Darcy Shen, in your repo, the toplevel directory contains misc/ src/ web/ I think we should only contains the src/ directory. misc/ and web/ are probably out of date and they are not "source code".
Multiplying repo is very confusing for potential contributors.
Plus, the new repo has no history issues and PR.

Why not keep the previous texmacs repo
and transfer misc and web to new texmacs.misc and texmacs.web repos ?

Ederag
Massimiliano Gubinelli
2018-06-20 18:28:08 UTC
Permalink
One reason I see is that in this way we have a full backup of the main svn TeXmacs repo, which could be useful something should happen to savannah (which happened in the past…).

Anyway one of the point of using git is that there is no “blessed” git repository. For TeXmacs the only official place is the svn repo, the git mirrors are just convenient for development but, as far as I see, pull requests should be integrated in svn by people allowed to do it.

I maintain my svn mirror for myself and for convenience for other people. In this way I can have multiple branches easily and test various configurations, but all the serious stuff reach the svn sooner or later. So as long as all the git mirrors fetch from svn there is no confusion possible. The only bad thing it could happen is that one mirror is not updated often enough.

Best
mg
Post by ederag
Post by sadhen
https://github.com/texmacs/GNUTeXmacs
PRs on any of the repos are welcome.
原始邮件
发送时间:2017年10月13日(周五) 19:34
主题:Re: [Texmacs-dev] Multiple "git svn" mirrors of texmacs on github, problems...?
Darcy Shen, in your repo, the toplevel directory contains misc/ src/ web/ I think we should only contains the src/ directory. misc/ and web/ are probably out of date and they are not "source code".
Multiplying repo is very confusing for potential contributors.
Plus, the new repo has no history issues and PR.
Why not keep the previous texmacs repo
and transfer misc and web to new texmacs.misc and texmacs.web repos ?
Ederag
_______________________________________________
Texmacs-dev mailing list
https://lists.gnu.org/mailman/listinfo/texmacs-dev
ederag
2018-06-20 20:35:21 UTC
Permalink
Post by Massimiliano Gubinelli
One reason I see is that in this way we have a full backup of the main svn TeXmacs repo, which could be useful something should happen to savannah (which happened in the past…).
Anyway one of the point of using git is that there is no “blessed” git repository. For TeXmacs the only official place is the svn repo, the git mirrors are just convenient for development but, as far as I see, pull requests should be integrated in svn by people allowed to do it.
I maintain my svn mirror for myself and for convenience for other people. In this way I can have multiple branches easily and test various configurations, but all the serious stuff reach the svn sooner or later. So as long as all the git mirrors fetch from svn there is no confusion possible. The only bad thing it could happen is that one mirror is not updated often enough.
This is true for the developer side.

But on the contributor side,
there are now 3 repos to check for issues or pull requests,
before filing one.

Ederag
Massimiliano Gubinelli
2018-06-20 21:00:02 UTC
Permalink
Post by ederag
Post by Massimiliano Gubinelli
One reason I see is that in this way we have a full backup of the main svn TeXmacs repo, which could be useful something should happen to savannah (which happened in the past…).
Anyway one of the point of using git is that there is no “blessed” git repository. For TeXmacs the only official place is the svn repo, the git mirrors are just convenient for development but, as far as I see, pull requests should be integrated in svn by people allowed to do it.
I maintain my svn mirror for myself and for convenience for other people. In this way I can have multiple branches easily and test various configurations, but all the serious stuff reach the svn sooner or later. So as long as all the git mirrors fetch from svn there is no confusion possible. The only bad thing it could happen is that one mirror is not updated often enough.
This is true for the developer side.
But on the contributor side,
there are now 3 repos to check for issues or pull requests,
before filing one.
Ederag
None of these repos is considered official as far as I know. The main developers works on savannah and there is already an official bug tracker there plenty of bugs awaiting willful contributors.

In my opinion it is interesting to send a pull request only to git repos owned by people who can actually commit the change into svn. And it make sense to choose the person you want to talk at. This is one of the point of the git philosophy, as far as I understand from Torvald’s talks on the subject.

So I do not see this as confusion. If you want to reach direcly the main developers (some of which do not use git) you need anyway to format a proper patch against the current svn repository (or any sufficiently up to date git mirror) and send it via mail or on savannah.

For contributors which do not need to maintain branches then I would suggest just to use the subversion repository, there is no gain in using git.

Personally I update a working tree from subversion to have the last changes and also I maintain a local mirrored git repo for all the more heavyweight branching and merging. This works just fine for the kind of development TeXmacs experiences.


Best
Max

Loading...