mainSavannah Administration - Support: sr #108460, ease.js: git push --force

 
 

sr #108460: ease.js: git push --force

Submitter:  Mike Gerwitz <mikegerwitz>
Submitted:  Tue 24 Dec 2013 01:38:30 AM UTC
   
 
Category:  Source code repositories - web browsing Priority:  5 - Normal
Severity:  4 - Important Status:  Done
Privacy:  Public Assigned to:  rwp
Operating System:  GNU/Linux Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 26 Dec 2013 10:09:54 PM UTC, comment #4: 

Yay!  Good to hear that everything is good now.  I removed the master.mistake and website.mistake safety copies I made so that things should be all normal now.

I may have come on a little strong.  Let me soften that up quite a bit.  I can see you understand and have the right attitude.  That was all I needed to hear.  Please don't get shy about doing things that need to be done pushing commits and that kind of things for fear of messing something up.  Stuff happens.  Everyone understands that and it isn't a big deal.  I have been on the other end of things as recently as today when I seriously broke something and needed a rescue!  We are all in this together.

So please keep up the good work and keep pushing updates and doing whatever needs to be done.  Life is good!  If you need anything please feel free to contact us either with a support request or with an email to -email is unavailable- either way.  Things only work when we all work together.

Bob Proulx <rwp>
Site Administrator
Thu 26 Dec 2013 01:53:50 PM UTC, comment #3: 

Thanks, Bob---this is taken care of; master is up-to-date and I was able to push to the website branch successfully.

> people have tried to suppress previously released source code
> in this way. This is specifically disabled due to this reason.


Absolutely---I'm supportive of this policy.

> This is clearly bad for anyone that has already pulled a copy
> from Savannah previously. Rewinding public branches is a bad
> thing.


I agree; the situations in which I do it are if I happen to commit something and immediately notice that there is a typo or missing file, so it's generally within a brief period of time. That said, diligence is better, and I will be exercising that instead now that ease.js has greater exposure and I'm not [one of the] one one(s) hitting the repository.

Thanks for your help!

Mike Gerwitz <mikegerwitz>
Site Administrator
Thu 26 Dec 2013 08:24:18 AM UTC, comment #2: 

As you know once you publish source code it is then published forever.  The general rule for public master branches is never to rewind public master branches.  We are especially cautious about doing so on Savannah because people have tried to suppress previously released source code in this way.  This is specifically disabled due to this reason.  Therefore I never simply remove source code lightly.  I always investigate in detail.

I cloned both projects and compared them.  I see three commits to master on Savannah that are identical to what are on gitorious but with different commit dates and therefore different commit hashes forcing a fork in the version history.  I can see that isn't a real difference and therefore I have gone ahead and rewound the head on Savannah to the last common commit between the two repositories.  You should be able to push your new version history to Savannah on top of this.

This is clearly bad for anyone that has already pulled a copy from Savannah previously.  Rewinding public branches is a bad thing.

I noticed that the project description for the web page was the default template.  I updated it.

Please let me know that you have uploaded your version history successfully and I will close out this ticket.  I branched master over to master.mistake and the same for website.  I will clean up by removing master.mistake when I know that all is good.  Let me know if there is anything else that needs to be done.

Bob Proulx <rwp>
Site Administrator
Tue 24 Dec 2013 09:00:13 PM UTC, comment #1: 

Sorry---this will need to be done with the website branch as well.

Mike Gerwitz <mikegerwitz>
Site Administrator
Tue 24 Dec 2013 01:38:30 AM UTC, original submission:  

I had rewritten the history of master a while back and have not been able to keep the savannah repository up to date with the other mirrors; would someone be able to help me with this be either deleting the repository or by updating master to that of git://gitorious.org/easejs/easejs.git?

Thanks!

Mike Gerwitz <mikegerwitz>
Site Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rwp (Posted a comment)
  • -email is unavailable- added by mikegerwitz (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-12-26 rwp StatusNeed Info Done
        Open/ClosedOpen Closed
    2013-12-26 rwp StatusNone Need Info
        Assigned toNone rwp

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code