Hi, On Wednesday, October 12, 2022 at 5:54:58 PM UTC-3 philip...@iee.email wrote:
> https://stackoverflow.com/a/954575/717355 may be a suitable answer that > matches what you are seeing. > this actually is not a question, but a potential bug report. I think git should not complain about the lack of the newline for symlinks. > > On Wednesday, October 12, 2022 at 9:06:01 PM UTC+1 > ignacio...@eclypsium.com wrote: > >> Hello, >> >> Sorry I forgot to mention I'm running a Linux system. >> >> Let me give you an example about how to reproduce this: >> >> - Clone git.git repo >> - *cd git* >> - l*n -s RelNotes RelNotes2* >> - *git add RelNotes2* >> - *git commit -m Test* >> - *git show* will display something like this: >> >> >> >> >> >> >> >> >> >> >> >> >> >> *commit 800c9cfa674e9c3e1d562c4c95699cc0094d6621 (HEAD -> master)Author: >> Ignacio Taranto <ignacio...@eclypsium.com>Date: Wed Oct 12 17:04:52 2022 >> -0300 Testdiff --git a/RelNotes2 b/RelNotes2new file mode 120000index >> 0000000..6efa746--- /dev/null+++ b/RelNotes2@@ -0,0 +1 @@+RelNotes* >> >> *\ No newline at end of file* >> >> >> >> On Wednesday, October 12, 2022 at 4:40:21 PM UTC-3 philip...@iee.email >> wrote: >> >>> Is this a Linux/*nix system, or a Windows (Git for Windows [GfW]) >>> system? >>> >>> It's important because Symlinks on nix systems are, as best I understand >>> it, a file system property, while on Windows it's emulated as a file (IIRC) >>> and the Git Index makes a note of that mode status. >>> >>> Can you show the actual setup and output that you are seeing. >>> >>> It wouldn't surprise me that the file, from the *nix dev view would not >>> have a terminating LF (Git does that a lot). >>> >>> If you actually have the git.git repo cloned, then look at the RelNotes >>> 'file'. On my GfW it has no LF terminator. >>> >>> On Wednesday, October 12, 2022 at 8:11:33 PM UTC+1 >>> ignacio...@eclypsium.com wrote: >>> >>>> So, both *git diff* and *git show* display "\ No newline at end of >>>> file" for symlinks. >>>> >>>> I think this doesn't make any sense since symlinks are not even regular >>>> files. >>>> >>>> I think this is a bug about how Git renders diffs for symlinks, I am >>>> making any sense here? >>>> >>>> Should I report this bug into the mailing list? >>>> >>> -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/203326c4-78df-4f9e-823b-b22514b0e352n%40googlegroups.com.
