You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
glock is a very slick project. I was wondering why the choice of GLOCKFILE for the filename? why not, Glockfile ?
.. perhaps the filename can be case insensitive, with the following support:
glock save github.com/my/project will generate GLOCKFILE as a default (to your preference) - as is. However, if a "glockfile" exists of any case, then it will write the contents in the filename of that case.
glock sync will look for any "glockfile" type-case
The text was updated successfully, but these errors were encountered:
Yeah, I guess I was thinking of files like README and INSTALL rather than Makefile or Godeps.
I don't mind changing it. Probably the ideal solution would be to (a) stop with an error if you notice more than one file named "glockfile" of any case, (b) read glockfile in any casing, and (c) write it with the casing "Glockfile". Or maybe that's overkill and just the simple change would be fine.
I'm not sure if git handles it properly, but I know that using HG, commits that change a file name casing (made on linux) could not be easily pulled on OSX due to file name conflicts / case insensitive file system.
Hello & happy NYE!
glock is a very slick project. I was wondering why the choice of
GLOCKFILE
for the filename? why not,Glockfile
?.. perhaps the filename can be case insensitive, with the following support:
glock save github.com/my/project
will generateGLOCKFILE
as a default (to your preference) - as is. However, if a "glockfile" exists of any case, then it will write the contents in the filename of that case.glock sync
will look for any "glockfile" type-caseThe text was updated successfully, but these errors were encountered: