> Actually, git reads
>
> # comment
>
> as 'ignore files with name "" (4 spaces)', and then a comment.
> It does not ignore the leading whitespace.
Even not as a comment, it treats it as literally a filename with
a hash and that comment in it. However, one (usually) does not
name their fil
> Note: the comments can be started away from the left margin,
> as normal in all unix-linux configuration files we know of.
> Git follows this behaviour fine.
Actually, git reads
# comment
as 'ignore files with name "" (4 spaces)', and then a comment.
It does not ignore the leading whit
Concerning ".gitignore", experienced using git 2.10.0
Starting code using one or more spaces or tabs from the left
margin will have git reading .gitignore and ignoring(or
un-ignoring) the command-instruction.
Example: Starting .gitignore
/*
# above line is duly read. Then un-ignoring
3 matches
Mail list logo
