From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: [PATCH 0/6] Update to a more recent Git
Date: Wed, 20 Mar 2013 21:21:41 +0100 [thread overview]
Message-ID: <CAHmME9oubSxsXzefncUAnKtxwFc928S23GoeGYG=1MJjbRg+3w@mail.gmail.com> (raw)
In-Reply-To: <cover.1362227260.git.john@keeping.me.uk>
On Sat, Mar 2, 2013 at 1:32 PM, John Keeping <john at keeping.me.uk> wrote:
> The changes here are reasonably straightforward, but v1.8.0 makes things
> a lot more difficult due to Git commit ba35480 (graph.c: mark private
> file-scope symbols as static, 2012-09-15). I'll see if Junio can be
> persuaded to revert that before trying anything too horrible here -
> without those methods we'll need to filter Git's graph output to convert
> ANSI colour escape sequences into HTML.
https://github.com/git/git/commit/c278e6f53d32ffdd475f9d4392cb6e5f5574e1ac
Looks like we're all set now. 1.8.3 should be a possibility now.
next prev parent reply other threads:[~2013-03-20 20:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 12:32 john
2013-03-02 12:32 ` [PATCH 1/6] Update git to v1.7.5.4 john
2013-03-02 15:12 ` Jason
2013-03-02 12:32 ` [PATCH 2/6] Update git to v1.7.6.5 john
2013-03-02 15:13 ` Jason
2013-03-02 12:32 ` [PATCH 3/6] Update git to v1.7.7.7 john
2013-03-02 15:19 ` Jason
2013-03-02 15:31 ` john
2013-03-02 15:39 ` Jason
2013-03-02 15:50 ` john
2013-03-04 4:53 ` Jason
2013-03-04 9:22 ` john
2013-03-04 14:18 ` Jason
2013-03-02 12:32 ` [PATCH 4/6] Update git to v1.7.8.6 john
2013-03-02 15:20 ` Jason
2013-03-02 12:32 ` [PATCH 5/6] Update git to v1.7.9.7 john
2013-03-02 15:21 ` Jason
2013-03-02 15:35 ` john
2013-03-02 15:39 ` Jason
2013-03-02 12:32 ` [PATCH 6/6] Update git to v1.7.12.4 john
2013-03-02 15:21 ` Jason
2013-03-02 15:06 ` [PATCH 0/6] Update to a more recent Git mailings
2013-03-02 15:08 ` Jason
2013-03-02 15:28 ` john
2013-03-02 15:32 ` Jason
2013-03-02 15:43 ` Jason
2013-03-02 15:44 ` mailings
2013-03-20 20:21 ` Jason [this message]
2013-03-20 20:28 ` john
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='CAHmME9oubSxsXzefncUAnKtxwFc928S23GoeGYG=1MJjbRg+3w@mail.gmail.com' \
--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).