From: john at keeping.me.uk (John Keeping)
Subject: [PATCH 1/1] git: update to v2.13.2
Date: Sat, 22 Jul 2017 12:01:49 +0100 [thread overview]
Message-ID: <20170722110149.GB1600@john.keeping.me.uk> (raw)
In-Reply-To: <20170705104515.02d96f85@leda>
On Wed, Jul 05, 2017 at 10:45:15AM +0200, Christian Hesse wrote:
> Christian Hesse <list at eworm.de> on Wed, 2017/07/05 10:43:
> > From: Christian Hesse <mail at eworm.de>
> >
> > Update to git version v2.13.2: With commit 8aee769f (pathspec: copy and free
> > owned memory) the definition of struct pathspec_item has changed with the
> > expectation that pathspecs will be managed dynamically. We work around this
> > a bit by setting up a static structure, but let's allocate the match string
> > to avoid needing to cast away const.
> >
> > Updated a patch from John Keeping <john at keeping.me.uk> for git v2.12.1.
>
> John, please complain if you want to send this in. ;)
No, I haven't had much time for CGit recently, so I'm happy for someone
else to take over!
prev parent reply other threads:[~2017-07-22 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 8:43 list
2017-07-05 8:45 ` list
2017-07-22 11:01 ` john [this message]
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=20170722110149.GB1600@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).