[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[savannah-help-public] [sr #109440] temporarily enable non-fast-forward
From: |
Bob Proulx |
Subject: |
[savannah-help-public] [sr #109440] temporarily enable non-fast-forward commits |
Date: |
Tue, 9 Jan 2018 13:20:18 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 |
Update of sr #109440 (project administration):
Status: None => In Progress
Assigned to: None => rwp
_______________________________________________________
Follow-up Comment #1:
Hello Alex,
I have opened the oddmuse repository for you to force push to it. Have have
saved off the old master just in case of tragedy.
Just a hint for the future, normally I personally prefer to have a commit that
I can roll master back in time to when things were considered good. Then you
can fix things and push an upload on top of it. That is safest for us as
curators of repositories because the rollback point is known. I looked but
couldn't figure it out for oddmuse. It looks like things are going to have to
go back in time quite far. I'll just say, please be careful out there.
Secondly if you want to discuss any git help please do email us at
savannah-help-public AT gnu.org and the group there would be happy to help
with things. It looks like git filter-branch may be the utility for you
depending upon what you are trying to do. Certainly pulling wouldn't make
things worse but will only merge in the upstream branch. Just don't pull,
merge, and then push or the push will publicly commit everything.
Please let me know when you have things back in a happy state. I will leave
the ticket open until then.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?109440>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/