From: Lars Schneider <larsxschneider@gmail.com>
To: Steve Hoelzer <shoelzer@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git-for-windows@googlegroups.com, git <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git for Windows 2.14.2(3)
Date: Tue, 17 Oct 2017 06:49:39 +0200 [thread overview]
Message-ID: <92D3AAC1-1775-4BF0-9DD6-810819C01AE8@gmail.com> (raw)
In-Reply-To: <CACbrTHcwjGLudp7WQta2bs_kitquj562rLqo8LAmRF5+d_RE=Q@mail.gmail.com>
> On 16 Oct 2017, at 20:59, Steve Hoelzer <shoelzer@gmail.com> wrote:
>
> Johannes,
>
> On Mon, Oct 16, 2017 at 5:57 AM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>> Hi Steve,
>>
>> On Sun, 15 Oct 2017, Johannes Schindelin wrote:
>>
>>> On Fri, 13 Oct 2017, Steve Hoelzer wrote:
>>>
>>>> On Thu, Oct 12, 2017 at 5:53 PM, Johannes Schindelin
>>>> <johannes.schindelin@gmx.de> wrote:
>>>>>
>>>>> It is my pleasure to announce that Git for Windows 2.14.2(3) is
>>>>> available from:
>>>>>
>>>>> https://git-for-windows.github.io/
>>>>>
>>>>> Changes since Git for Windows v2.14.2(2) (October 5th 2017)
>>>>>
>>>>> New Features
>>>>>
>>>>> * Comes with Git LFS v2.3.3.
>>>>
>>>> I just ran "git update" and afterward "git version" reported
>>>> 2.14.2(3), but "git lfs version" still said 2.3.2.
>>>>
>>>> I also uninstalled/reinstalled Git for Windows and LFS is still 2.3.2.
>>>
>>> Ah bummer. I forgot to actually update it in the VM where I build the
>>> releases :-(
>>>
>>> Will work on it tomorrow.
>>
>> I'll actually use this opportunity to revamp a part of Git for Windows'
>> release engineering process to try to prevent similar things from
>> happening in the future.
>>
>> Also, cURL v7.56.1 is slated to be released in exactly one week, and I
>> have some important installer work to do this week, so I'll just defer the
>> new Git for Windows version tentatively to Monday, 23rd.
>>
>> Git LFS users can always install Git LFS v2.3.3 specifically in the
>> meantime, or use Git for Windows' snapshot versions
>> (https://wingit.blob.core.windows.net/files/index.html).
>
> Sounds like a good plan.
>
> I think I have successfully updated to LFS 2.3.3 by copying the new
> git-lfs.exe into C:\Program Files\Git\mingw64\bin. Is that right way
> to do it?
That's how I do it and that's how the Git LFS installer will (hopefully)
do it in the future, too: https://github.com/git-lfs/git-lfs/issues/2587
- Lars
next prev parent reply other threads:[~2017-10-17 4:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 22:53 [ANNOUNCE] Git for Windows 2.14.2(3) Johannes Schindelin
2017-10-13 12:48 ` Steve Hoelzer
2017-10-15 15:11 ` Johannes Schindelin
2017-10-16 10:57 ` Johannes Schindelin
2017-10-16 18:59 ` Steve Hoelzer
2017-10-17 4:49 ` Lars Schneider [this message]
2017-10-17 9:03 ` Johannes Schindelin
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=92D3AAC1-1775-4BF0-9DD6-810819C01AE8@gmail.com \
--to=larsxschneider@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=shoelzer@gmail.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).