Johannes, On Mon, Oct 16, 2017 at 5:57 AM, Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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@xxxxxx> 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? Thanks, Steve
