From: list at eworm.de (Christian Hesse)
Subject: [PATCH 1/1] git: update to v2.10.1, again
Date: Wed, 12 Oct 2016 14:04:37 +0200 [thread overview]
Message-ID: <20161012120437.3868-1-list@eworm.de> (raw)
From: Christian Hesse <mail at eworm.de>
Commit 1b46645db24efe8758ed9654ee625d3375821f13 accidentally reverted to
git v2.10.0. So update again.
Signed-off-by: Christian Hesse <mail at eworm.de>
---
git | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git b/git
index 6ebdac1..6406bdc 160000
--- a/git
+++ b/git
@@ -1 +1 @@
-Subproject commit 6ebdac1bab966b720d776aa43ca188fe378b1f4b
+Subproject commit 6406bdc0b95715a087fdeeb0f6adf3deb80a25b8
--
2.10.0
reply other threads:[~2016-10-12 12:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20161012120437.3868-1-list@eworm.de \
--to=cgit@lists.zx2c4.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).