From: "Torsten Bögershausen" <tboegi@web.de>
To: Anthony Sottile <asottile@umich.edu>
Cc: Eric Sunshine <sunshine@sunshineco.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH] config.c: fix regression for core.safecrlf false
Date: Wed, 13 Jun 2018 03:19:23 +0200 [thread overview]
Message-ID: <20180613011923.GA5772@atze2.lan> (raw)
In-Reply-To: <CA+dzEBk8H_=a9k1DaFUK=JJBhd17bhS3+ngSUBcBV+7hD-RFMw@mail.gmail.com>
On Mon, Jun 11, 2018 at 06:46:34PM -0700, Anthony Sottile wrote:
[]
> Anything else for me to do here? (sorry! not super familiar with the process)
Your patch has been picked up by Junio, and is currently merged into the
"pu" branch (proposed updates):
commit bc8ff8aec33836af3fefe1bcd3f533a1486b793f
Merge: e69b544a38 6cb09125be
Author: Junio C Hamano <gitster@pobox.com>
Date: Tue Jun 12 10:15:13 2018 -0700
Merge branch 'as/safecrlf-quiet-fix' into jch
Fix for 2.17-era regression.
* as/safecrlf-quiet-fix:
config.c: fix regression for core.safecrlf false
From there, it will typically progress into next and master,
unless reviewers come with comments and improvements.
You can watch out for "What's cooking in git" messages here on the list
to follow the progress.
From my experience it will end up in a Git release, but I don't know,
if it will be 2.18 or a later one.
prev parent reply other threads:[~2018-06-13 1:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 20:17 [PATCH] config.c: fix regression for core.safecrlf false Anthony Sottile
2018-06-06 15:53 ` Torsten Bögershausen
2018-06-06 17:15 ` Eric Sunshine
2018-06-06 17:17 ` Eric Sunshine
2018-06-06 17:18 ` Anthony Sottile
2018-06-06 17:22 ` Eric Sunshine
2018-06-12 1:46 ` Anthony Sottile
2018-06-12 4:34 ` Eric Sunshine
2018-06-13 1:19 ` Torsten Bögershausen [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180613011923.GA5772@atze2.lan \
--to=tboegi@web.de \
--cc=asottile@umich.edu \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).