On Sat, Jan 7, 2017 at 1:14 AM, Bruce Momjian wrote:
> On Wed, Jan 4, 2017 at 10:05:10AM -0500, Tom Lane wrote:
>> Andres Freund writes:
>> > On 2017-01-03 13:02:28 -0500, Bruce Momjian wrote:
>> >> Yeah, I was doing parallel pulls of different branches in git via shell
>> >> script, and it seem
On Wed, Jan 4, 2017 at 10:05:10AM -0500, Tom Lane wrote:
> Andres Freund writes:
> > On 2017-01-03 13:02:28 -0500, Bruce Momjian wrote:
> >> Yeah, I was doing parallel pulls of different branches in git via shell
> >> script, and it seems the size of this commit showed me that doesn't
> >> work.
On Wed, Jan 04, 2017 at 11:54:07AM -0800, David Fetter wrote:
> On Wed, Jan 04, 2017 at 02:20:52PM -0500, Tom Lane wrote:
> > David Fetter writes:
> > >>> Actually, my takeaway from this was "don't ever use git reset on
> > >>> the repo".
> >
> > > That's actually not tenable. If we ever find so
On Wed, Jan 04, 2017 at 02:20:52PM -0500, Tom Lane wrote:
> David Fetter writes:
> >>> Actually, my takeaway from this was "don't ever use git reset on
> >>> the repo".
>
> > That's actually not tenable. If we ever find something in our
> > repo that we don't have full rights to, especially if i
David Fetter writes:
>>> Actually, my takeaway from this was "don't ever use git reset on
>>> the repo".
> That's actually not tenable. If we ever find something in our repo
> that we don't have full rights to, especially if it's something that
> would put roadblocks in front of people who'd lik
On Wed, Jan 04, 2017 at 04:08:20PM +0100, Magnus Hagander wrote:
> On Wed, Jan 4, 2017 at 4:05 PM, Tom Lane wrote:
> > Andres Freund writes:
> > > On 2017-01-03 13:02:28 -0500, Bruce Momjian wrote:
> > >> Yeah, I was doing parallel pulls of different branches in git
> > >> via shell script, and i
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Andres Freund writes:
> > On 2017-01-03 13:02:28 -0500, Bruce Momjian wrote:
> >> Yeah, I was doing parallel pulls of different branches in git via shell
> >> script, and it seems the size of this commit showed me that doesn't
> >> work. Sorry.
>
> > Shou
On Wed, Jan 4, 2017 at 4:05 PM, Tom Lane wrote:
> Andres Freund writes:
> > On 2017-01-03 13:02:28 -0500, Bruce Momjian wrote:
> >> Yeah, I was doing parallel pulls of different branches in git via shell
> >> script, and it seems the size of this commit showed me that doesn't
> >> work. Sorry.
Andres Freund writes:
> On 2017-01-03 13:02:28 -0500, Bruce Momjian wrote:
>> Yeah, I was doing parallel pulls of different branches in git via shell
>> script, and it seems the size of this commit showed me that doesn't
>> work. Sorry.
> Shouldn't you check the results of something like this be
On 2017-01-03 13:02:28 -0500, Bruce Momjian wrote:
> Yeah, I was doing parallel pulls of different branches in git via shell
> script, and it seems the size of this commit showed me that doesn't
> work. Sorry.
Shouldn't you check the results of something like this before pushing?
Sorry for piling
On Tue, Jan 3, 2017 at 06:57:44PM +0100, Magnus Hagander wrote:
> I'm leaning for +1 for resetting. It'll be a pain for any mirrors of the
> repo, but I think the clean history is worth it.
>
>
>
> It seems bruce pushed a whole bunch of merge conflicts, and possibly more. I
> think h
On Tue, Jan 3, 2017 at 6:59 PM, Heikki Linnakangas wrote:
> On 01/03/2017 07:57 PM, Magnus Hagander wrote:
>
>> On Tue, Jan 3, 2017 at 6:54 PM, Heikki Linnakangas
>> wrote:
>>
>> On 01/03/2017 07:49 PM, Bruce Momjian wrote:
>>>
>>> On Tue, Jan 3, 2017 at 06:46:32PM +0100, Magnus Hagander wrote:
On 01/03/2017 07:57 PM, Magnus Hagander wrote:
On Tue, Jan 3, 2017 at 6:54 PM, Heikki Linnakangas wrote:
On 01/03/2017 07:49 PM, Bruce Momjian wrote:
On Tue, Jan 3, 2017 at 06:46:32PM +0100, Magnus Hagander wrote:
Is this a big enough boo that we actually want to reset the master repo
to
On Tue, Jan 3, 2017 at 6:54 PM, Heikki Linnakangas wrote:
> On 01/03/2017 07:49 PM, Bruce Momjian wrote:
>
>> On Tue, Jan 3, 2017 at 06:46:32PM +0100, Magnus Hagander wrote:
>>
>>> Is this a big enough boo that we actually want to reset the master repo
>>> to get
>>> rid of it?
>>>
>>> If so, we
On 01/03/2017 07:49 PM, Bruce Momjian wrote:
On Tue, Jan 3, 2017 at 06:46:32PM +0100, Magnus Hagander wrote:
Is this a big enough boo that we actually want to reset the master repo to get
rid of it?
If so, we need to do it *now* beore people get a chance to mirror it properly..
Thoughts?
If
On Tue, Jan 3, 2017 at 06:46:32PM +0100, Magnus Hagander wrote:
> Is this a big enough boo that we actually want to reset the master repo to get
> rid of it?
>
> If so, we need to do it *now* beore people get a chance to mirror it
> properly..
>
> Thoughts?
>
> If not, just a revert should wor
Sorry, this will be reverted and redone.
---
On Tue, Jan 3, 2017 at 05:38:05PM +, Bruce Momjian wrote:
> Update copyright for 2017
>
> Backpatch-through: certain files through 9.2
>
> Branch
> --
> REL9_2_STABLE
>
17 matches
Mail list logo
