public inbox for [email protected]  

help / color / mirror / Atom feed

From: Stephen Frost <[email protected]>
To: Andrew Dunstan <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Subject: Re: git failures
Date: Tue, 03 Jan 2017 22:46:11 +0000
Message-ID: <CAOuzzgomWboThBE9Nto7ZzsqMrB6nLyYT-1Aoy5ZgRdhAdBEtw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
List-Unsubscribe:  <mailto:[email protected]?body=unsub%20buildfarm-members>

Andrew, Tom,

Out of the office currently but will address as soon as I'm able to.

Thanks!

Stephen

On Tue, Jan 3, 2017 at 17:21 Tom Lane <[email protected]> wrote:

> Andrew Dunstan <[email protected]> writes:
>
> > Recently a number of git failures have been seen like this:
>
> >     *** Please tell me who you are.
>
> > Notably on Debian/Ubuntu machines. I assume they have had some sort of
>
> > recent git update.
>
>
>
> No, I do not think it's the fault of the buildfarm machines.  The problem
>
> is that Magnus got rid of a bad commit into the 9.2 branch via "git reset"
>
> not "git revert", cf
>
>
>
>
> https://www.postgresql.org/message-id/CABUevEzrD-BYtQOQ22navkoWquOC5TcqPcBS_iQ2cYqaK9_39g%40mail.gma...
>
>
>
> and these three machines seem to have been quick enough to see the
>
> intermediate state and get confused by it.  I'm not very sure why "git
>
> pull" isn't enough to recover, but it evidently isn't.
>
>
>
>                         regards, tom lane
>
>
>
>

view thread (12+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: git failures
  In-Reply-To: <CAOuzzgomWboThBE9Nto7ZzsqMrB6nLyYT-1Aoy5ZgRdhAdBEtw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox