Repository navigation
removing dead branches? #154
Description
Hi all,
I was wondering whether a clean-up of obviously dead branches might be useful.
(mainly for reading comfort while changing branches )
Here is a list of the branches which could be easily removed:
- branch AAA: This branch is 1410 commits behind master. no commit ahead of.
- branch update_Edgar: This branch is 1804 commits behind master. no commit ahead of.
- branch gnss_make_rinex: This branch is 1259 commits behind master. no commit ahead of.
- branch revert-38-master: This branch is 1 commit ahead of, 1749 commits behind master. The single commit is a correction of the GipsyX server address, and the associated pull request is marked as closed.
Activity
beaudu commentedon Nov 8, 2024
OK, good idea to clean-up all.
PierreS-alpha commentedon Nov 10, 2024
Branches mentioned above have been deleted
@jmsaurel, what is the status of the branches:
jmsaurel commentedon Nov 11, 2024
Hello @PierreS-alpha
This project was intended to allow the production of ad-hoc spectrogram when working on a MC3 event.
I think the objective have been implemented with the sefran spectrogram option.
This branch can be deleted.
There have been some related work on this in Martinique, but I'm not sure it is similar or as complete.
This branch should be kept.
The PR #115 is still pending to incorporate those modifications.
But the PR should be rebased or something like because there is only the latest commit to merge.
The branch should be kept, the PR cleaned and accepted.
The proposed modification in this branch seems to have already incorporated (make sure every readfmtdata_ code at least return an empty D.e error matrix).
This branch can be deleted.
This branch contains all the modifications and bug fixes made up to 2023 in Guadeloupe.
Not all of them have been reviewed or incorporated.
This branch should be kept.
Still working on this one from time to time.
This branch should be kept.