install data files below ${prefix}/share/sakia (not ${prefix}/sakia)
install data files below ${prefix}/share/sakia (not ${prefix}/sakia) to comply with File Hierarchy Standard (FHS)
Merge request reports
Activity
@jonas, thanks for your contributions.
Can you do future merge requests only on
dev
branch, please?I have 10+ years experience juggling with git: Yes, I am aware that I can rebase the commit onto a different branch.
Question remains: Is a rebase what you request that I do, @vtexier ?
Thanks to @moul for the hint, you can edit your MR, then you should modify the target branch to
dev
instead ofmaster
.After that, you surely have to rebase your work on the last
dev
branch head, as I just modify it today.Then I will approve and merge your changes.
Do not hesitate to ask if you have questions.
Edited by Vincent Texier@jonas, please, can you edit your MRs to merge onto dev branch ?
Click on the edit button at the top right, then you'll see this :
Edit Merge Request !788
From jonas/sakia:wip/data_path into clients/python/sakia: master
Use the branch selector displaying master and choose dev.
Then update all your branch on your git (with your 10+ years experience I am sure it will not be a problem) and force push your branch again.
Thanks.
PS: Question remains: Is a rebase what you request that I do, response is YES, on dev branch.
But... You HAVE TO change your MRs to merge on the dev branch too.
Hope it helps.
added 6 commits
-
d79572dd...7acdf0b3 - 5 commits from branch
clients/python:dev
- 1e0a6338 - install data files below ${prefix}/share/sakia (not ${prefix}/sakia) to comply...
-
d79572dd...7acdf0b3 - 5 commits from branch
Sorry Jonas, but Sakia is not maintained anymore. See https://forum.duniter.org/t/fin-du-developpement-de-sakia/7851