Jim Nasby writes:
> On 10/3/13 12:49 PM, Magnus Hagander wrote:
>> We could also use git receive hooks, but those would be very hard to
>> override when you*do* need to modify the files (which you might
>> within a release).
> You can have the receive hook ignore the condition on existence of a
On 10/3/13 12:49 PM, Magnus Hagander wrote:
We could also use git receive hooks, but those would be very hard to
override when you*do* need to modify the files (which you might
within a release).
You can have the receive hook ignore the condition on existence of a file. It's
kinda kludgey, bu
On Wed, Oct 2, 2013 at 1:17 PM, Jim Nasby wrote:
> On 9/29/13 9:41 PM, Andrew Dunstan wrote:
>> On 09/29/2013 10:38 PM, Peter Eisentraut wrote:
>>>
>>> On Sun, 2013-09-29 at 22:33 -0400, Andrew Dunstan wrote:
Well if these are not meant to be changed then not being able to write
the
On Wed, Oct 2, 2013 at 7:17 PM, Jim Nasby wrote:
> On 9/29/13 9:41 PM, Andrew Dunstan wrote:
>>
>>
>> On 09/29/2013 10:38 PM, Peter Eisentraut wrote:
>>>
>>> On Sun, 2013-09-29 at 22:33 -0400, Andrew Dunstan wrote:
Well if these are not meant to be changed then not being able to write
>>
On 9/29/13 9:41 PM, Andrew Dunstan wrote:
On 09/29/2013 10:38 PM, Peter Eisentraut wrote:
On Sun, 2013-09-29 at 22:33 -0400, Andrew Dunstan wrote:
Well if these are not meant to be changed then not being able to write
them in your git repo might be a clue to that.
Git doesn't support setting
On 09/29/2013 10:38 PM, Peter Eisentraut wrote:
On Sun, 2013-09-29 at 22:33 -0400, Andrew Dunstan wrote:
Well if these are not meant to be changed then not being able to write
them in your git repo might be a clue to that.
Git doesn't support setting file permissions other than the executable
On Sun, 2013-09-29 at 22:33 -0400, Andrew Dunstan wrote:
> Well if these are not meant to be changed then not being able to write
> them in your git repo might be a clue to that.
Git doesn't support setting file permissions other than the executable
bit, so this is a nonstarter.
--
Sent via
On 09/29/2013 09:58 PM, Peter Eisentraut wrote:
On Fri, 2013-09-27 at 13:23 -0400, Andrew Dunstan wrote:
This was lazy and there's no real excuse, although I will note that it
was a mistake far too easy to make. Perhaps as a warning indicator we
should remove write permissions from these files.
On Fri, 2013-09-27 at 13:23 -0400, Andrew Dunstan wrote:
> This was lazy and there's no real excuse, although I will note that it
> was a mistake far too easy to make. Perhaps as a warning indicator we
> should remove write permissions from these files.
What do you mean by that?
> See attached
When adding json support to hstore, I made a major blunder and added the
new functionality to the existing sql script instead of bumping the
version, renaming the script and adding an update script.
This was lazy and there's no real excuse, although I will note that it
was a mistake far too
10 matches
Mail list logo
