> From: Alcolo Alcolo
> Because C can be a base commit of branches and merges, then it's a
> nightmare to rebase.
>
> I know that scripts exists to rebase merges (based on git-rev-list,
> git-cat-file, git-hash-object/git-commit-tree), but those scripts redo the
> git-filter-branch job.
Actu
Nevermind I guess the sticky bit trickles down throughout the whole
directory structure.
On Friday, October 24, 2014 2:31:15 PM UTC-4, Jon Zeolla wrote:
>
> My concern with commit-only permission restrictions are that I would need
> to allow the ability for everyone who can push to directl
My concern with commit-only permission restrictions are that I would need
to allow the ability for everyone who can push to directly edit
/etc/files/environments/{production,development}/*,
which could break a lot of things in this environment.
What are your thoughts on adding the sticky bit
Because C can be a base commit of branches and merges, then it's a
nightmare to rebase.
I know that scripts exists to rebase merges (based on git-rev-list,
git-cat-file, git-hash-object/git-commit-tree), but those scripts redo the
git-filter-branch job.
Honestly, I'm not really capable of dea
On Thu, Oct 23, 2014 at 12:30:09PM -0700, Jon Zeolla wrote:
> Hi Konstantin,
>
> I apologize - it appears that all of the objects in this directory
> are owned by the individual who pushes them, but it seemed like an
> anomaly because my file permissions script overwrote all of the
> older file pe
