No, not like that. See here:
https://git.wiki.kernel.org/index.php/GitCommunity
The email address you send the "subscribe" message to is NOT the mailing list
itself.
What you just did is send the words "subscribe git" to everyone already on the
mailing list :)
-Original Message-
From: g
Yay! Feel free to tweak and/or butcher the wording, I won't be offended :)
-Original Message-
From: Torsten Bögershausen [mailto:tbo...@web.de]
Sent: Friday, August 16, 2019 12:20 AM
To: Yagnatinsky, Mark
Cc: 'Junio C Hamano' ; 'git@vger.kernel.org'
Su
Okay, first attempt at better phrasing. This may need more paragraph breaks,
or something.
Right now it's very wall-of-texty. And probably in a style way too different
from the rest of the git docs.
Also, the syntax is probably closer to markdown than AsciiDoc; sorry.
Anyway, enough disclaimers
Turns out that this is not intentional behavior of IntelliJ but an unfortunate
interaction with a bug in git.
Had I been using a more recent version of git, it wouldn't be happening.
https://youtrack.jetbrains.com/issue/IDEA-205601
Patched docs on the way eventually. Hopefully it's okay if my sy
> Would you like to elobarate which IDE that is?
IntelliJ from JetBrains. I'm planning on emailing them to at least mention
this somewhere in their own docs, because I think it's not there.
Will attempt revised wording soon-ish, but not promising today.
-
Thank you once more. Finally, I believe I understood everything you said.
I was about to say that this contradicts my own experience.
But then I remembered that I normally use my IDE rather than the command line.
And I just checked that indeed that the behavior of my IDE is totally different!
It r
Okay, let me be more explicit :)
Suppose "git check-attr -a ." produces no output.
Now, is predictable?
-Original Message-
From: git-ow...@vger.kernel.org [mailto:git-ow...@vger.kernel.org] On Behalf Of
Junio C Hamano
Sent: Monday, August 12, 2019 2:19 PM
To: Yagnatinsky
Okay, I feel like I'm on the verge of understanding, but it keeps eluding me,
because you keep answering the question I actually asked, rather than the
one I should have asked... let me try again, and bear with me if it seems like
I'm
repeating the same question over and over, because I don't unde
But I don't even have a git attributes file! There's no attribute flipping
going on, I think.
The CRLF'd file was committed by someone else on my team, who probably has git
configured differently than I do.
Or am I missing the point?
-
Wait a second... suppose a file is committed with CRLF line endings.
You're saying that even if I have autocrlf set to "input" or "auto", the file
will never get "converted" to LF format unless I explicitly renormalize?
That sounds like a fairly sensible behavior, but it's not what I've observed i
After correcting spelling of renormalize, the end result of the script you gave
is that line endings in working directory are CRLF, and in the repo are LF.
Is that expected? Surprising? Not sure what you were trying to test there. I
also fixed my script to use printf, new version is:
(using co
Okay, my attempt at better wording for the docs is not going well, because it
turns I that I still don't understand the behavior here!
I thought that "input" means that CRLF will become LF on "git add" but that
seems to be true only sometimes.
For instance, consider the following 11-line shell sc
> Yes, do I read this as "I will send a patch" ?
Probably not, but you can read it as "I will cook up better wording and reply
to this thread"
--
This message, and any attachments, is for the intended recipient(s) only, may
cont
I hope this is the right mailing list, hope someone will redirect me if not...
The git documentation (git help config) for core.autocrlf doesn't mention that
false is a valid option; it only mentions true and input.
Further, the docs for "input" are misleading, in that they lead the reader to
ass
14 matches
Mail list logo
