From: john at keeping.me.uk (John Keeping)
Subject: [PATCH 0/4] Advance to git 2.14
Date: Tue, 8 Aug 2017 13:54:50 +0100 [thread overview]
Message-ID: <20170808125450.GR1600@john.keeping.me.uk> (raw)
In-Reply-To: <20170808120305.22938-1-whydoubt@gmail.com>
On Tue, Aug 08, 2017 at 07:03:01AM -0500, Jeff Smith wrote:
> This set of patches advances git to v2.14, and makes the neccessary
> changes in cgit to build with it. My ui-blame changes depend on
> v2.14 and will thus depend on these changes.
I haven't pulled this to test, but it looks like the following patches
are all build fixes without which the initial commit doesn't build. If
that is the case, these should be squashed to a single patch.
"git rebase -x 'make test' master" should succeed when run on a branch
containing these patches.
> Jeff Smith (4):
> git: update to v2.14
> git v2.14: use object_id structure for hashes
> git v2.14: include config.h when needed
> git v2.14: change how ignore-case is specified
>
> Makefile | 2 +-
> git | 2 +-
> scan-tree.c | 5 +++--
> shared.c | 6 +++---
> ui-blob.c | 6 +++---
> ui-clone.c | 2 +-
> ui-commit.c | 6 +++---
> ui-diff.c | 18 +++++++++---------
> ui-log.c | 10 +++++-----
> ui-patch.c | 4 ++--
> ui-plain.c | 2 +-
> ui-snapshot.c | 2 +-
> ui-tag.c | 4 ++--
> ui-tree.c | 18 +++++++++---------
> 14 files changed, 44 insertions(+), 43 deletions(-)
>
> --
> 2.9.4
next prev parent reply other threads:[~2017-08-08 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 12:03 whydoubt
2017-08-08 12:03 ` [PATCH 1/4] git: update to v2.14 whydoubt
2017-08-08 12:03 ` [PATCH 2/4] git v2.14: use object_id structure for hashes whydoubt
2017-08-08 12:03 ` [PATCH 3/4] git v2.14: include config.h when needed whydoubt
2017-08-08 12:03 ` [PATCH 4/4] git v2.14: change how ignore-case is specified whydoubt
2017-08-08 12:54 ` john [this message]
2017-08-10 0:02 ` [PATCH v2] git: update to v2.14 whydoubt
2017-08-10 6:16 ` list
2017-08-10 10:32 ` john
2017-08-10 13:58 ` Jason
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=20170808125450.GR1600@john.keeping.me.uk \
--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).