Skip to content

Commit 515bc07

Browse files
committed
FAQ: recommend upgrading to v2.50.1 or later
That version comes with security bug fixes. Signed-off-by: Johannes Schindelin <[email protected]>
1 parent e9b4386 commit 515bc07

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ In the meantime you could try:
4040

4141
In general, yes: it is a good idea to stay up-to-date.
4242

43-
If you have a version older than 2.47.1(2), it is *highly* advisable to upgrade. A couple of Git versions came with important fixes to security-relevant vulnerabilities: 2.47.1(2), 2.45.1, 2.40.1, 2.39.2, 2.39.1, 2.38.1, 2.37.1, 2.36.0, 2.35.3, 2.35.3, 2.30.2, 2.30.0(2), 2.29.2(3), 2.29.2(2), 2.26.1, 2.24.1(2), 2.17.1(2), 2.14.1, 2.7.4, 2.7.0, 2.6.1, 2.5.2, 1.9.5-preview20150319, and 1.9.5-preview20141217.
43+
If you have a version older than 2.50.1, it is *highly* advisable to upgrade. A couple of Git versions came with important fixes to security-relevant vulnerabilities: 2.50.1, 2.47.1(2), 2.45.1, 2.40.1, 2.39.2, 2.39.1, 2.38.1, 2.37.1, 2.36.0, 2.35.3, 2.35.3, 2.30.2, 2.30.0(2), 2.29.2(3), 2.29.2(2), 2.26.1, 2.24.1(2), 2.17.1(2), 2.14.1, 2.7.4, 2.7.0, 2.6.1, 2.5.2, 1.9.5-preview20150319, and 1.9.5-preview20141217.
4444

4545
## How do I update *Git for Windows* upon new releases?
4646

0 commit comments

Comments
 (0)