From: Jeff King <peff@peff.net>
To: Johannes Sixt <j6t@kdbg.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"René Scharfe" <l.s.r@web.de>,
"X H" <music_is_live_lg@hotmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] check_and_freshen_file: fix reversed success-check
Date: Thu, 9 Jul 2015 18:48:30 -0400 [thread overview]
Message-ID: <20150709224830.GA24998@peff.net> (raw)
In-Reply-To: <559EDEE6.1040807@kdbg.org>
On Thu, Jul 09, 2015 at 10:51:50PM +0200, Johannes Sixt wrote:
> >Ah! That code is less than a year old. When I began to adopt a workflow
> >requiring force-pushes lately, I wondered why I haven't seen these
> >failures earlier, because I did do force pushes in the past, but not
> >that frequently. I thought that I had just been lucky. But this would
> >explain it.
>
> And, in fact, with this patch these particular failures are gone! Thank you
> so much!
Great, thanks for testing. You can temper your appreciation by noticing
that I introduced the bug in the first place. ;)
-Peff
next prev parent reply other threads:[~2015-07-09 22:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 13:45 Git force push fails after a rejected push (unpack failed)? X H
2015-07-07 14:13 ` Jeff King
[not found] ` <DUB120-W36B78FEE6DC80BDCB05D7FF6920@phx.gbl>
2015-07-07 19:49 ` Jeff King
2015-07-07 23:05 ` Eric Sunshine
2015-07-08 17:41 ` Johannes Sixt
2015-07-08 18:05 ` Jeff King
2015-07-08 18:33 ` [PATCH] check_and_freshen_file: fix reversed success-check Jeff King
2015-07-08 19:24 ` Junio C Hamano
2015-07-08 20:33 ` [PATCH v2] " Jeff King
2015-07-08 21:03 ` [PATCH] " Johannes Sixt
2015-07-09 20:51 ` Johannes Sixt
2015-07-09 22:48 ` Jeff King [this message]
2015-07-11 22:21 ` X H
2015-07-13 3:52 ` Jeff King
2015-07-13 19:58 ` X H
2015-07-08 20:28 ` Git force push fails after a rejected push (unpack failed)? X H
2015-07-08 20:56 ` Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150709224830.GA24998@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=l.s.r@web.de \
--cc=music_is_live_lg@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.