Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Project Hosting on Google Code
Home
+ new post
About this group
Join this group
Message from discussion can we please get issue 5821 fixed?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Augie Fackler  
View profile  
 More options May 3 2012, 11:20 am
From: Augie Fackler <au...@google.com>
Date: Thu, 3 May 2012 10:20:14 -0500
Local: Thurs, May 3 2012 11:20 am
Subject: Re: can we please get issue 5821 fixed?
Print | View thread | Show original | Report this message | Find messages by this author

On Thu, May 3, 2012 at 5:51 AM, tri...@samba.org <tridg...@gmail.com> wrote:
> The ArduPilot project just lost a bunch of commits in our git
> repository because of this bug. A user who was not experienced with
> git did a forced push of an old checkout on top of our master
> repository, then other people who got the resulting pull errors tried
> to fix it by doing pushes of their own.
> I've sorted it out by restoring from one of my own clones and bringing
> in all the missing commits I could find, but this really is just a
> disaster waiting to happen with all git based projects on
> code.google.com.
> It is normal when running a shared git repository to prevent this like
> this:

> [receive]
>        denyNonFastforwards = true
>        denyDeletes = true

> It not only prevents mistakes like what happened to us today, it is
> also an important security measure. It is only a matter of time before
> some malicious user rewrites the history of a project in a subtle way
> to introduce a security hole. That is much harder to get away with if
> you can only do fast forward pushes.
> So _please_ can we get an administrative option to set the above
> options on our repositories?

Star the issue so we get an idea of its relative importance. I'd
(personally) like to have this option, but it's not a trivial amount
of engineering work as we don't run cgit on normal storage (it's
mostly custom storage).
> Cheers, Tridge

> --
> You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group.
> To post to this group, send email to google-code-hosting@googlegroups.com.
> To unsubscribe from this group, send email to google-code-hosting+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google