-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"First-Time Git Setup" docs about .gitconfig are incorrect as of Git For Windows v2.24 #1717
Comments
I'd say ignore the really old stuff. 😉 People should not be using a version of Git for Windows that old anyway. 👻 What do you think @ben? |
That sounds right to me.
On Thu, Dec 2, 2021 at 2:02 AM HonkingGoose ***@***.***> wrote:
Or we could simply ignore versions of GFW that are 2+ years old:
On Windows systems, Git looks for the global .gitconfig file in the
%USERPROFILE% directory (C:\Users\%USERNAME% for most people). It also
looks for the system config file at [path]/etc/gitconfig, where [path] is
wherever Git was installed on your system.
I'd say ignore the really old stuff. 😉 People should not be using a
version of Git for Windows that old anyway. 👻
What do you think @ben <https://github.com/ben>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1717 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAJXXT2JHWD4MNXOJ2DUPDUO4737ANCNFSM5JE5IYBA>
.
--
– Ben
|
2023-10-27 So I tried following Chapter 1 of the current version, and followed along trying to use the latest information to get set up, and I have to say that something is missing. I have no clue how to use GIT, and this didn't help me get set up using GIT for Windows and trying to connect to my GIT account. Please consider getting someone who doesn't know GIT to use your instructions without your help, then fix them so that people who are new to all this can actually figure it out. BTW, I'm on 2.42.0.Windows.2 |
Hey, now it's 5 years old! <g>
Citing "C:\Users%USERNAME%" is a bit dangerous since, as stated, it's for "most people" but not "all people". For example, my Windows setup at the office has a local user "christian" and my AD user "christian" also, so "%USERNAME%" points to "christian" but %USERPROFILE% points to "c:\users\christian.MYDOMAIN". Since %USERPROFILE% already points to the right location anyway, I'd rephrase this simply as
|
There's no existing/similar bug report.
This report is about a single actionable bug.
This report is about the ProGit book, version 2, English language.
Bug covers book website/pdf
Problem is present in the Pro Git book on the website?
Which version of the book is affected?
Source files
Describe the bug:
On this page, there is the following paragraph (emphasis mine):
As of git-for-windows/git#2358, this is incorrect. As described in the release notes:
Steps to reproduce:
Expected behavior:
I think we could change this to say something like:
Or we could simply ignore versions of GFW that are 2+ years old:
Screenshots:
No response
Additional context:
No response
Device
No response
Operating system
No response
Browser/application + version
No response
The text was updated successfully, but these errors were encountered: