From: Jeff King <peff@peff.net>
To: Gennaro Torre <gtorre@tumblr.com>
Cc: git@vger.kernel.org
Subject: Re: issue upgrading git from 1.8.2.1 to 2.8.0
Date: Fri, 22 Apr 2016 19:14:52 -0400 [thread overview]
Message-ID: <20160422231452.GA10905@sigill.intra.peff.net> (raw)
In-Reply-To: <CA+UAp04e9-CcUJ+2fheHGw1q6MS6smyHhvyw34NeoT7HbKgnnQ@mail.gmail.com>
On Fri, Apr 22, 2016 at 06:44:02PM -0400, Gennaro Torre wrote:
> When we upgraded to 2.8.0, all nodes received the upgrade.
>
> We observed that when we tried to deploy code to the nodes (they run
> `git fetch` to update the repository) this would fail.
Did `git fetch` say anything interesting on stderr?
-Peff
next prev parent reply other threads:[~2016-04-22 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 22:44 issue upgrading git from 1.8.2.1 to 2.8.0 Gennaro Torre
2016-04-22 22:48 ` Stefan Beller
2016-04-22 22:57 ` Junio C Hamano
2016-04-22 23:14 ` Jeff King [this message]
[not found] ` <CA+UAp06YMrVY8rK3jzWtLB=Zo8F=GTLQByYD-xR8+Lj=3=_hqg@mail.gmail.com>
2016-04-23 5:11 ` Jeff King
[not found] ` <CA+UAp04M+jxS1JBPuz78GovopKSjvgkEdOj2DYG6wF7inasvWA@mail.gmail.com>
2016-04-23 5:22 ` Jeff King
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=20160422231452.GA10905@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gtorre@tumblr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).