On Tue, 3 Jan 2023, folkert wrote:
Lost me. What about sntp do you want to put on gitlab?
Oh, reading these in reverse order. I think you are offering to
add this as a Merge Request on GitLab? Yes, that would be good.
Can I please send the patch via e-mail? I've been struggeling with
gitlab for an hour and whatever I do it keeps complaining that I'm not
allowed to push to the project (my own clone, in a branch).
You don't push to the "project" - you start by forking the project on GitLab
and then cloning the fork. It's useful to also add the main repo as an
additional remote, frequently called "upstream", so you can update with new
upstream changes as needed.
I did that.
Once you have that setup, you push your local branch with the intended
changes to your fork, and then create a merge request from there. The setup
part above is a one-time thing.
I also did that.
That's why I'm confused why I get this error.
Although this specific change was already merged, it's still useful to fix
your setup for future use.
Is your remote setup using git (ssh) remote specs or https (the gadgets on
the website offer both)? I suppose there's probably some way to do an
appropriately authenticated push via https, but I don't know what it is.
With git/ssh, as long as you've uploaded a suitable public key to GitLab,
then authentication is via ssh key.
You should have a setup something like this:
MacPro:ntpsec fw$ git remote -v
origin g...@gitlab.com:fhgwright/ntpsec.git (fetch)
origin g...@gitlab.com:fhgwright/ntpsec.git (push)
upstream g...@gitlab.com:NTPsec/ntpsec.git (fetch)
upstream g...@gitlab.com:NTPsec/ntpsec.git (push)
If that's correct, then make sure you're pushing to 'origin', not
'upstream'.
Fred Wright
_______________________________________________
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
