ip
On 21/10/2019 23:05, Johannes Schindelin wrote:
Team,
a couple of days later than I wanted, but at least it is now here:
https://github.com/git-for-windows/git/releases/tag/v2.24.0-rc0.windows.1
Please test...
Thank you,
Johannes
Team,
a couple of days later than I wanted, but at least it is now here:
https://github.com/git-for-windows/git/releases/tag/v2.24.0-rc0.windows.1
Please test...
Thank you,
Johannes
Hi all,
I tried pretty hard yesterday to get a preview of Git for Windows out,
based on v2.24.0-rc0, but I need a bit more time.
The PR at https://github.com/git-for-windows/git/pull/2360 shows where I
am going, and I started the automation based on it, but it failed (and I
could not monkey
Since this is a git-gui dialog/prompt, why not use the git-gui icon?
This will mean some uniformity between all the platforms (though I'm not
sure if other platforms even use GIT_ASK_YESNO). It would also probably
save you the hacks needed to find out the git-for-windows icon.
Well, the
From: Johannes Schindelin
For additional GUI goodness.
Signed-off-by: Johannes Schindelin
---
git-gui--askyesno | 12
1 file changed, 12 insertions(+)
diff --git a/git-gui--askyesno b/git-gui--askyesno
index 45b0260eff..c0c82e7cbd 100755
--- a/git-gui--askyesno
+++ b/git-gui--ask
This is another set of patches from Git for Windows' fork that have been
sitting there since 2010, providing cross-platform GUI helpers to ask the
user a question or allow typing in a password.
This patch series was first submitted as
https://github.com/patthoyts/git-gui/pull/5 which was ig
Dear Git users,
It is my pleasure to announce that Git for Windows 2.23.0 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.22.0 (June 8th 2019)
New Features
* Comes with Git v2.23.0.
* Comes with patch level 3 of the MSYS2 runtime (Git for Windows
Team,
seeing as v2.23.0 is just around the corner, I decided on skipping a
full Git for Windows release for v2.22.1: while the list of patches
between v2.22.0 and v2.22.1 is extensive, nothing sticks out to me that
says that we need a new Git for Windows only to release another one in
six days
t
> url = git://repo.or.cz/alt-git.git
> url = https://github.com/gitster/git
The corresponding Git for Windows v2.23.0-rc2 can be found here:
https://github.com/git-for-windows/git/releases/tag/v2.23.0-rc2.windows.1
Please test as much as you can.
Thanks!
Johannes
>
> New contributors who
Hi Jadian,
On Fri, Aug 09, 2019 at 12:31:12AM -0500, Jadian Radiator wrote:
> Git For Windows' installer can't see my Atom installation.
> I got Atom directly from Atom's official site.
This is the Git mailing list, which does not answers questions about Git
for Windows, o
Git For Windows' installer can't see my Atom installation.
I got Atom directly from Atom's official site.
I think git can't see it because of this unfortunate fact.
It doesn't let you choose where to install,
and it installs to your appdata folder.
Any idea what I need to do?
:
>
> https://www.kernel.org/pub/software/scm/git/testing/
The corresponding Git for Windows v2.23.0-rc1 can be found here:
https://github.com/git-for-windows/git/releases/tag/v2.23.0-rc1.windows.1
Thanks,
Johannes
On Fri, Aug 02, 2019 at 09:53:55AM -0700, Junio C Hamano wrote:
> Jonathan Nieder writes:
>
> > We'll also want to update the docs. And as Todd suggests, we should
> > cover how to disable mailmap in tests.
> >
> > Signed-off-by: Jonathan Nieder
> > ---
>
> I avoided the "don't bother initial
Jonathan Nieder writes:
> We'll also want to update the docs. And as Todd suggests, we should
> cover how to disable mailmap in tests.
>
> Signed-off-by: Jonathan Nieder
> ---
I avoided the "don't bother initializing use_mailmap_config to
unknown" simplification, but I guess the change is clea
Junio C Hamano wrote:
> I suspect that you may have misread the "is interactive" bit in the
> original; that was used only to decide if we are going to warn.
Ah. That was indeed confusing. Anyway, it's nice to see the complexity
go away.
[...]
> +++ b/builtin/log.c
[...]
> @@ -214,12 +204,8 @@
Junio C Hamano wrote:
> Junio C Hamano writes:
>
>> Jeff King writes:
>>
+ if (mailmap < 0)
mailmap = 0;
- }
>>>
>>> This should be "mailmap = 1" to match the commit message, no? (Which
>>> also implies we may want a new test).
>>
[...]
> +test_expect_success 'log.mai
Junio C Hamano writes:
> Jeff King writes:
>
>>> + if (mailmap < 0)
>>> mailmap = 0;
>>> - }
>>
>> This should be "mailmap = 1" to match the commit message, no? (Which
>> also implies we may want a new test).
>
> Gaa, of course.
-- >8 --
From: Junio C Hamano
Date: Thu, 1 Aug 20
Jeff King writes:
>> +if (mailmap < 0)
>> mailmap = 0;
>> -}
>
> This should be "mailmap = 1" to match the commit message, no? (Which
> also implies we may want a new test).
Gaa, of course.
> I'd also be OK with leaving it at "0" for now, making a note of the
> upcoming cha
for
> > > testing at the usual places. It is comprised of 420 non-merge
> > > commits since v2.22.0, contributed by 62 people, 23 of which are
> > > new faces.
> > >
> > > The tarballs are found at:
> > >
> > > https://www.kernel
Hi,
On Wed, 31 Jul 2019, Ariadne Conill wrote:
> Hello,
>
> On Wed, Jul 31, 2019 at 10:21 PM Junio C Hamano wrote:
> >
> > Jeff King writes:
> >
> > > This seems OK to me, though I kind of wonder if anybody really wants
> > > "auto". Unlike log.decorate, which changes the syntax, there is no re
On Thu, Aug 01, 2019 at 08:45:54AM -0700, Junio C Hamano wrote:
> While I think "revert to hardcoded default" may be a good idea, I do
> not think the hardcoded default you implemented that changes the
> behaviour based on the output destination makes much sense. If I
> want to eradicate jun...@c
Hello,
On Thu, Aug 1, 2019 at 10:46 AM Junio C Hamano wrote:
>
> Jonathan Nieder writes:
>
> > Although as Dscho mentions, it's particularly irritating because it is
> > not part of the paginated output.
> > ...
> > Let's bite the bullet and jump straight to --use-mailmap in case (4).
> >
> > Wh
Jonathan Nieder writes:
> Although as Dscho mentions, it's particularly irritating because it is
> not part of the paginated output.
> ...
> Let's bite the bullet and jump straight to --use-mailmap in case (4).
>
> While at it, add a new log.mailmap setting "auto" that can be used to
> explicitly
Hello,
On Wed, Jul 31, 2019 at 10:21 PM Junio C Hamano wrote:
>
> Jeff King writes:
>
> > This seems OK to me, though I kind of wonder if anybody really wants
> > "auto". Unlike log.decorate, which changes the syntax, there is no real
> > reason to avoid mailmap when somebody else is parsing the
Jeff King writes:
> This seems OK to me, though I kind of wonder if anybody really wants
> "auto". Unlike log.decorate, which changes the syntax, there is no real
> reason to avoid mailmap when somebody else is parsing the output. And I
> could imagine it is especially confusing if:
>
> git log
On Wed, Jul 31, 2019 at 08:38:14PM -0500, Ariadne Conill wrote:
> > Something like:
> >
> > Author: A U Thor
> > Original-Author: I M Mailmapped
> >
> > gives even more information while leaving the "Author:" line untouched.
> > But in introducing a new line, it may also be breaking somebody
Hello,
On Wed, Jul 31, 2019 at 8:00 PM Jeff King wrote:
>
> On Wed, Jul 31, 2019 at 05:21:25PM -0700, Jonathan Nieder wrote:
>
> > Although as Dscho mentions, it's particularly irritating because it is
> > not part of the paginated output.
> >
> > I wonder if the ideal might not be to trigger it
Jeff King wrote:
> This seems OK to me, though I kind of wonder if anybody really wants
> "auto".
Sure. It's just the usual way of handling the lack of support for an
"unset" directive in git's config syntax (for example, if a script
author wants to test the default behavior).
Thanks,
Jonathan
since v2.22.0, contributed by 62 people, 23 of which are
> > new faces.
> >
> > The tarballs are found at:
> >
> > https://www.kernel.org/pub/software/scm/git/testing/
>
> And a corresponding Git for Windows v2.23.0-rc0 can be found here:
>
> https://github
On Wed, Jul 31, 2019 at 05:21:25PM -0700, Jonathan Nieder wrote:
> Although as Dscho mentions, it's particularly irritating because it is
> not part of the paginated output.
>
> I wonder if the ideal might not be to trigger it more selectively, when
> the output actually changed due to a reflog e
Hello,
On Wed, Jul 31, 2019 at 7:21 PM Jonathan Nieder wrote:
>
> Jeff King wrote:
>
> > I think part of what my annoyance is responding to (and your willingness
> > to just squelch this for everybody) is that switching this particular
> > default isn't really that big a deal, that it requires an
Jeff King wrote:
> I think part of what my annoyance is responding to (and your willingness
> to just squelch this for everybody) is that switching this particular
> default isn't really that big a deal, that it requires annoying people
> on every single "git log" invocation. Perhaps we would be b
On Wed, Jul 31, 2019 at 02:43:10PM +0200, Johannes Schindelin wrote:
> And a corresponding Git for Windows v2.23.0-rc0 can be found here:
>
> https://github.com/git-for-windows/git/releases/tag/v2.23.0-rc0.windows.1
>
> Please test!
>
> One (slightly annoying) issue I fo
balls are found at:
>
> https://www.kernel.org/pub/software/scm/git/testing/
And a corresponding Git for Windows v2.23.0-rc0 can be found here:
https://github.com/git-for-windows/git/releases/tag/v2.23.0-rc0.windows.1
Please test!
One (slightly annoying) issue I found already is that a `git log
Dear Git users,
It is my pleasure to announce that Git for Windows 2.22.0 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.21.0 (February 26th 2019)
New Features
* Comes with Git v2.22.0.
* The awk included in Git for Windows now includes extensions
Team,
I was a bit too tired last night to wait for the trusty Azure Pipelines to
finish publishing this preview, so with a bit of delay, here comes the
announcement:
https://github.com/git-for-windows/git/releases/tag/v2.22.0-rc3.windows.1
Thanks,
Johannes
On Mon, 3 Jun 2019, Junio C Hamano
Team,
here is the corresponding Git for Windows v2.22.0-rc2:
https://github.com/git-for-windows/git/releases/tag/v2.22.0-rc2.windows.1
So far, I am rather happy with the robustness of the release candidates,
but please y'all: test!
Thanks,
Johannes
On Thu, 30 May 2019, Junio C Hamano
Great, thanks for the feedback.
Version 2.21 was also working BTW.
Bye
Pierre
-Original Message-
From: Johannes Schindelin
Sent: Tuesday, March 12, 2019 18:09
To: Garcia, Pierre
Cc: git@vger.kernel.org
Subject: RE: Bug: git for Windows spawning a lot of processes recursively
Hi Pierre
Hi Pierre,
On Mon, 11 Mar 2019, Garcia, Pierre wrote:
> Hello Johannes,
>
> I installed the following snapshot on the problematic machine:
> Sun, 10 Mar 2019 17:37:25 +0100
> (commit eb5d06f545)
> Git for Windows installer: 64-bit
>
> And the problem is gone! No mo
Hello Johannes,
I installed the following snapshot on the problematic machine:
Sun, 10 Mar 2019 17:37:25 +0100
(commit eb5d06f545)
Git for Windows installer: 64-bit
And the problem is gone! No more issue!
At the time I had the issue I was on field trip with limited time and no other
version to
Hi Pierre,
On Fri, 22 Feb 2019, Garcia, Pierre wrote:
> I'd like to report an issue with git for Windows
>
> Git version 2.20.1
> Windows 7 x64 (Build 7601: Service Pack 1)
>
>
> Issue:
&g
Team,
the corresponding Git for Windows v2.21.0 will probably be published on
Tuesday, as we are waiting for a Git LFS version that fixes a known
regression that is considered critical.
In the meantime, feel free to grab the current snapshot (which differs
from the final v2.21.0 probably only in
Hello,
I'd like to report an issue with git for Windows
Git version 2.20.1
Windows 7 x64 (Build 7601: Service Pack 1)
Issue:
When running from Git-bash (not even inside a repo), git commands from built-in
are OK
Team,
the Git for Windows v2.21.0-rc pre-release followed suite last night:
https://github.com/git-for-windows/git/releases/tag/v2.21.0-rc2.windows.1
Please test (and don't worry when I don't reply during the next few days,
please, I'll reply, no worries).
Ciao,
Johannes
On T
Dear Git users,
It is my pleasure to announce that Git for Windows 2.20.1 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.20.0 (December 10th 2018)
New Features
* Comes with Git v2.20.1.
* Comes with cURL v7.63.0.
Bug Fixes
* Fixes a speed
Team,
sorry for the inconvenience, but I had to "pull" Git for Windows v2.19.2
because of two major bugs: 32-bit Git Bash simply failed to start, and all
operations using git:// URLs were broken.
This close to v2.20.0, I was uncomfortable pushing yet another upgrade to
users that would
starting the git bash two windows pop up instead of one.
> One that's "empty" and the other one containing the real git bash.
Thank you for the report. This has been also reported at
https://github.com/git-for-windows/git/issues/1942, and I fixed it in the
meantime.
Ciao,
Johannes
On Wed, Nov 21, 2018 at 11:28:28AM -0800, Bryan Turner wrote:
> But that test code exists because Bitbucket Server provides a Java API
> [1][2] which allows third-party developers to easily build arbitrary
> Git commands to invoke for their own functionality. Setting
> `GitBranchCreateBuilder.refl
, 23 of which are
>> new faces.
>
> The "for Windows" flavor of Git v2.20.0-rc0 is available here:
>
> https://github.com/git-for-windows/git/releases/tag/v2.20.0-rc0.windows.1
>
> The current change log for v2.20.0 reads like this:
>
> Changes since Git for
On Wed, Nov 21, 2018 at 6:20 AM Jeff King wrote:
>
> On Tue, Nov 20, 2018 at 03:17:07PM -0800, Bryan Turner wrote:
>
> > I've run 2.20.0-rc0 through the test matrix for Bitbucket Server on
> > both Linux and Windows, and the only failures were related to this
> > change:
> >
> > * "git branch -l "
On Tue, Nov 20, 2018 at 03:17:07PM -0800, Bryan Turner wrote:
> I've run 2.20.0-rc0 through the test matrix for Bitbucket Server on
> both Linux and Windows, and the only failures were related to this
> change:
>
> * "git branch -l " used to be a way to ask a reflog to be
>created while creat
On Tue, Nov 20, 2018 at 12:57 PM Johannes Schindelin
wrote:
>
> Team,
>
> On Sun, 18 Nov 2018, Junio C Hamano wrote:
>
> > An early preview release Git v2.20.0-rc0 is now available for
> > testing at the usual places. It is comprised of 887 non-merge
> > commits since v2.19.0, contributed by 71 p
ws" flavor of Git v2.20.0-rc0 is available here:
https://github.com/git-for-windows/git/releases/tag/v2.20.0-rc0.windows.1
The current change log for v2.20.0 reads like this:
Changes since Git for Windows v2.19.1 (Oct 5th 2018)
Please note: Git CMD is deprecated as of this Git for Windows vers
Hi,
I use git-repo which makes use of Git for Windows and also uses the
gpg tool bundled in Git for Windows.
I am able to run the git-repo with Git-2.18.0-64-bit.exe, but recently
I updated the Git to new release of Git for Windows 2.19.1 and that
does not work with git-repo tool. I found that
Dear Git users,
It is my pleasure to announce that Git for Windows 2.19.1 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.19.0 (September 11th 2018)
New Features
* Comes with Git v2.19.1.
* Comes with Git LFS v2.5.2.
* Comes with Git Credential
From: Johannes Schindelin
Previously, we only ever declared a target Windows version if compiling
with Visual C.
Which meant that we were relying on the MinGW headers to guess which
Windows version we want to target...
Let's be explicit about it, in particular because we actually want to
bump t
On Tue, Oct 02, 2018 at 06:56:29AM +, peter.doll...@mt.com wrote:
> Please see my original observation below.
> Is it possible, to extend the git-log syntax in the way, that it
> accepts the short -L option (without :file) of blame in unique cases
> (only one file is logged or respectively the
: Dienstag, 2. Oktober 2018 01:06
An: git-for-windows/git
Cc: Dolland Peter MTPCE; Mention
Betreff: Re: [git-for-windows/git] log -L//,+1 not accepted (#1856)
It would be appropriate, but what @PhilipOakley asked you, @pdolland, was
whether this is Windows-specific behavior. Because if it is not
On Fri, Sep 28 2018, Jonathan Nieder wrote:
> Ævar Arnfjörð Bjarmason wrote:
>> On Thu, Sep 27 2018, Jonathan Nieder wrote:
>
>>> That said, that seems to me like a lot of work to avoid adding some
>>> patches to "next" that belong in "next"
On Fri, Sep 28, 2018 at 09:57:11PM +0200, Ævar Arnfjörð Bjarmason wrote:
> Another way to look at it, which is closer to what I was thinking about,
> is to just view GFW as some alternate universe "next" branch (which by
> my count is ~2-3k commits ahead of master[1]).
> 1. $ git log --max-parents
Ævar Arnfjörð Bjarmason wrote:
> On Thu, Sep 27 2018, Jonathan Nieder wrote:
>> That said, that seems to me like a lot of work to avoid adding some
>> patches to "next" that belong in "next" anyway. I understand why the
>> Git for Windows maintai
gt; recall one offhand that's quite similar to GFW v.s. git.git.
>>
>> My only stake in this is I thought it would be neat to be able to "apt
>> install git-for-windows", but I understand there's a support burden, but
>> if some *nix packagers are inter
On Thu, Sep 27, 2018 at 6:24 PM Ævar Arnfjörð Bjarmason
wrote:
> My only stake in this is I thought it would be neat to be able to "apt
> install git-for-windows",
That's what private builds are for (or "PPA" if debian has an
equivalent). I already largely ignor
only stake in this is I thought it would be neat to be able to "apt
> install git-for-windows", but I understand there's a support burden, but
> if some *nix packagers are interested, maybe never taking it out of the
> Debian equivalent of "experimental" and sayi
t have "alternates" and are semi
or permanently forked, like emacs & xemacs, JDK etc., although I can't
recall one offhand that's quite similar to GFW v.s. git.git.
My only stake in this is I thought it would be neat to be able to "apt
install git-for-windows", bu
On 9/27/2018 12:01 PM, Ævar Arnfjörð Bjarmason wrote:
I had an IRC conversation with Johannes saying I didn't know Git For
Windows builds perfectly well for Linux, this just isn't advertised in
the ANNOUNCE E-Mails, so I hadn't tried.
We run CI to ensure it builds and tests
Ævar Arnfjörð Bjarmason wrote:
> GFW is a "friendly fork", but a permanent one it seems. The diff between
> it and 2.19.0 proper is ~10k lines, and e.g. this last release had
> experimental stash/rebase in C that 2.19.0 didn't.
>
> So it would be great if this were packaged up by linux distro as s
I had an IRC conversation with Johannes saying I didn't know Git For
Windows builds perfectly well for Linux, this just isn't advertised in
the ANNOUNCE E-Mails, so I hadn't tried.
Johannes doesn't build his own tarballs, but these are provided at:
https://github.com/git-
Dear Git users,
It is my pleasure to announce that Git for Windows 2.19.0 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.18.0 (June 22nd 2018)
New Features
* Comes with Git v2.19.0.
* There are now fast, built-in versions of git stash and git rebase
Team,
the corresponding Git for Windows v2.19.0-rc1 (most notably with the
Experimental Options page in the installer letting you opt into using the
built-in `stash` and `rebase`) was built by Jameson Miller (and me) last
night and can be found here:
https://github.com/git-for-windows/git
Team,
On Fri, 24 Aug 2018, Johannes Schindelin wrote:
> while this mail talks about Git for Windows, please keep in mind that we
> try *very* hard to keep Git for Windows' master working correctly not only
> on Windows but also on macOS and Linux.
>
> I, for one, run Gi
Dear Git users,
It is my pleasure to announce that Git for Windows 2.18.0 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.17.1(2) (May 29th 2018)
New Features
* Comes with Git v2.18.0.
* Comes with Git Credential Manager v1.16.2.
Bug Fixes
* The
Dear Git users,
It is my pleasure to announce that Git for Windows 2.17.1(2) is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.17.0 (April 3rd 2018)
New Features
* Comes with Git v2.17.1.
* Comes with Perl v5.26.2.
* The installer now offers VS Code
Dear Git users,
It is my pleasure to announce that Git for Windows 2.17.0 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.16.3 (March 23rd 2018)
New Features
* Comes with Git v2.17.0.
* Comes with OpenSSL v1.0.2o.
* Comes with Git Credential
Dear Git users,
It is my pleasure to announce that Git for Windows 2.16.3 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.16.2 (February 20th 2018)
New Features
* Comes with Git v2.16.3.
* When choosing to "Use Git from the Windows Command P
Dear Git users,
It is my pleasure to announce that Git for Windows 2.16.2 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.16.1(4) (February 7th 2018)
New Features
* Comes with Git v2.16.2.
* For every new Git for Windows version, .zip archives
Hi Bryan,
On Fri, 16 Feb 2018, Bryan Turner wrote:
> On Fri, Feb 16, 2018 at 3:30 PM, Johannes Schindelin
> wrote:
> > Hi team,
> >
> > I am unwilling to release Git for Windows v2.16.2 on a Friday night, but I
> > have something almost as good. Ther
On Fri, Feb 16, 2018 at 3:30 PM, Johannes Schindelin
wrote:
> Hi team,
>
> I am unwilling to release Git for Windows v2.16.2 on a Friday night, but I
> have something almost as good. There is a snapshot available here:
>
>
> https://urldefense.proofpoi
Hi team,
I am unwilling to release Git for Windows v2.16.2 on a Friday night, but I
have something almost as good. There is a snapshot available here:
https://wingit.blob.core.windows.net/files/index.html
That snapshot brings quite a few updated components apart from Git proper
(such as
Dear Git users,
It is my pleasure to announce that Git for Windows 2.16.1(4) is available from:
https://git-for-windows.github.io/
Changes since Git for Windows v2.16.1(3) (February 6th 2018)
Bug Fixes
* When called from TortoiseGit, git.exe can now spawn processes again
Dear Git for Windows SDK users,
[This mail only concerns the *SDK* of Git for Windows, i.e. the build
environment to work on, and contribute to, Git for Windows.]
On Tue, 6 Feb 2018, Johannes Schindelin wrote:
> Changes since Git for Windows v2.16.1(2) (February 2nd 2018)
>
> New
Dear Git users,
It is my pleasure to announce that Git for Windows 2.16.1(3) is available from:
https://git-for-windows.github.io/
Changes since Git for Windows v2.16.1(2) (February 2nd 2018)
New Features
* Git for Windows' SDK packages are now hosted on Azure Blobs, fixing
Hi all, in particular packagers,
On Fri, 2 Feb 2018, Johannes Schindelin wrote:
> It is my pleasure to announce that Git for Windows 2.16.1(2) is
> available from:
>
> https://git-for-windows.github.io/
Typically, every Git for Windows version is accompanied with updates t
Dear Git users,
It is my pleasure to announce that Git for Windows 2.16.1(2) is available from:
https://git-for-windows.github.io/
The main purpose of this out-of-band release is to update the BusyBox, cURL,
Perl and Heimdal components to newer versions.
Changes since Git for Windows
Dear Git users,
It is my pleasure to announce that Git for Windows 2.16.1 is available from:
https://git-for-windows.github.io/
Changes since Git for Windows v2.16.0(2) (January 18th 2018)
This is a hotfix release, based on upstream Git's hotfix to address a
possible segmentation
Dear Git users,
It is my pleasure to announce that Git for Windows 2.16.0(2) is available from:
https://git-for-windows.github.io/
Changes since Git for Windows v2.15.1(2) (November 30th 2017)
Git for Windows now has a new homepage: https://gitforwindows.org/ (it
is still graciously
ls are found at:
>
> https://www.kernel.org/pub/software/scm/git/testing/
And the corresponding Git for Windows files can be found here:
https://github.com/git-for-windows/git/releases/tag/v2.16.0-rc2.windows.1
Please test! (Probably the best way is to install the portable Git
side-by-side wit
Cygwin's Bash does (and hence the MSYS2 Bash used by Git for
Windows, too).
Then the MSYS2 Bash calls git.exe, which is *not* an MSYS2 program, hence
the MSYS2 runtime knows that it has to convert the path lists to Windows
paths separated by semicolons.
The next thing happening in our case i
Am 30.11.2017 um 02:50 schrieb Johannes Schindelin:
> Hi all,
>
> unfortunately, a last-minute bug slipped in: MSYS2 updated vim (including
> its defaults.vim, in a way that interacted badly with Git for Windows'
> configuration). The result was that an ugly warning is shown
Hi all,
unfortunately, a last-minute bug slipped in: MSYS2 updated vim (including
its defaults.vim, in a way that interacted badly with Git for Windows'
configuration). The result was that an ugly warning is shown every time a
user opens vim (which is still the default editor of Git for Wi
as it could\should greatly help
> Windows people in lowering friction in first encounter with Git (for
> Windows).
>
> Being pretty unfamiliar with Linux and its tools at the time, I
> remember the initial frustration in trying to do what otherwise felt
> as a no-brain, simple and tri
encounter with Git (for
Windows).
Being pretty unfamiliar with Linux and its tools at the time, I
remember the initial frustration in trying to do what otherwise felt
as a no-brain, simple and trivial task - write the damn commit
message after `git commit`, lol. Even had to kill the bash windo
Dear Git users,
It is my pleasure to announce that Git for Windows 2.15.1 is available from:
https://git-for-windows.github.io/
Changes since Git for Windows v2.15.0 (October 30th 2017)
New Features
* Comes with Git v2.15.1.
* Operations in massively-sparse worktrees are now much
Hi team,
On Mon, 30 Oct 2017, Johannes Schindelin wrote:
> It is my pleasure to announce that Git for Windows 2.15.0 is available from:
>
> https://git-for-windows.github.io/
By the way, to everybody who tested the RC2: thank you so much. You caught
three bugs. Three bugs tha
Dear Git users,
It is my pleasure to announce that Git for Windows 2.15.0 is available from:
https://git-for-windows.github.io/
Changes since Git for Windows v2.14.3 (October 23rd 2017)
New Features
* Comes with Git v2.15.0.
Bug Fixes
* The auto-updater tried to run at a precise
>> wrote:
>>>>
>>>> [cutting linux-kernel]
>>>>
>>>> On Fri, 20 Oct 2017, Junio C Hamano wrote:
>>>>
>>>>> A release candidate Git v2.15.0-rc2 is now available for testing
>>>>> at the usual plac
20 Oct 2017, Junio C Hamano wrote:
> >>
> >>> A release candidate Git v2.15.0-rc2 is now available for testing
> >>> at the usual places.
> >>
> >> The Git for Windows equivalent is now available from
> >>
> >> https://github
elease candidate Git v2.15.0-rc2 is now available for testing
>>> at the usual places.
>>
>> The Git for Windows equivalent is now available from
>>
>> https://github.com/git-for-windows/git/releases/tag/v2.15.0-rc2.windows.1
>
> Hi Dscho,
>
> I
> On 21 Oct 2017, at 00:22, Johannes Schindelin
> wrote:
>
> Hi team,
>
> [cutting linux-kernel]
>
> On Fri, 20 Oct 2017, Junio C Hamano wrote:
>
>> A release candidate Git v2.15.0-rc2 is now available for testing
>> at the usual places.
>
> Th
Dear Git users,
On Tue, 24 Oct 2017, Johannes Schindelin wrote:
> Dear Git users,
>
> It is my pleasure to announce that Git for Windows 2.14.3 is available from:
>
> https://git-for-windows.github.io/
... and at this point, usually the release notes are repeated. In
1 - 100 of 383 matches
Mail list logo
