List for cgit developers and users
 help / color / mirror / Atom feed
From: andy at (Andy Green)
Subject: [PATCH 1/1] RFC: git: update to v2.18.0-rc2
Date: Mon, 18 Jun 2018 14:42:26 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20180618081010.2381bbcd@leda>

On 06/18/2018 02:10 PM, Christian Hesse wrote:
> Christian Hesse <list at> on Thu, 2018/06/14 00:52:
>> Update to git version v2.18.0-rc2. Required changes follow upstream commits:
> I've pushed John's snapshot series to ch/for-jason. Does anybody agree that
> we want that? I will rebase the final commit on ch/for-jason then.

FWIW ch/for-jason, with your v2.18.0-rc2 patch on top, and then my stuff 
is here


> _______________________________________________
> CGit mailing list
> CGit at

      reply	other threads:[~2018-06-18  6:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 22:52 list
2018-06-14  1:48 ` [PATCH] ui-shared: typename changed to type_name in git 2.18.0-rc2 andy
2018-06-16 16:14 ` [PATCH 1/1] RFC: git: update to v2.18.0-rc2 john
2018-06-16 16:15   ` Jason
2018-06-16 20:34   ` list
2018-06-18  6:10 ` list
2018-06-18  6:42   ` andy [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \

* 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).