.gitignore: don;t accidentally ignore some files
authorDouglas Bagnall <douglas.bagnall@catalyst.net.nz>
Thu, 21 Apr 2016 04:13:42 +0000 (16:13 +1200)
committerGarming Sam <garming@samba.org>
Tue, 3 May 2016 06:10:10 +0000 (08:10 +0200)
commitc2649352e0917c3c2bcf1b7ad74d73d21e73be9c
tree14c44edbe5b2ab23b5cc40daad966ee16686ccd7
parent3751ffbbe75524984a822d65f623a040ca79c8f7
.gitignore: don;t accidentally ignore some files

The previous first line of .gitignore ("bin/") correctly ignored the
bin/ directory, but it also ignored the git controlled content in
source4/scripting/bin.  The correct line is "/bin/", as explained in
these snippets from the gitignore documentation:

    If the pattern ends with a slash, it is removed for the purpose
    of the following description, but it would only find a match with
    a directory. In other words, foo/ will match a directory foo and
    paths underneath it, but will not match a regular file or a
    symbolic link foo (this is consistent with the way how pathspec
    works in general in Git).

    A leading slash matches the beginning of the pathname. For example,
    "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".

Signed-off-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Garming Sam <garming@catalyst.net.nz>
.gitignore