Re: info/exclude not working
I wouldn't worry too much about this use case, we have a pretty lame workflow On Mon, Jun 3, 2013 at 1:32 PM, Jeff King wrote: > On Mon, Jun 03, 2013 at 01:04:39PM -0700, Devin Rhode wrote: > >> MBP:dish devin$ cat ../.git/info/exclude >> # git ls-files --others --exclude-from=.git/info/exclude >> # Lines that start with '#' are comments. >> # For a project mostly in C, the following would be a good set of >> # exclude patterns (uncomment them if you want to use them): >> # *.[oa] >> # *~ >> models/CAFE.json >> dish/models/CAFE.json >> >> MBP:dish devin$ git status >> # On branch master >> # Changes not staged for commit: >> # (use "git add ..." to update what will be committed) >> # (use "git checkout -- ..." to discard changes in working directory) >> # >> # modified: models/CAFE.json ***Shouldn't appear > > The exclude mechanism does not mean "do not ever look at this file". It > means "when you are adding untracked files, do not include this one". > Somebody has already added the file to the repository before your > exclude was in place, so it is a tracked file. > > There is currently no official mechanism in git to do what you want > (there are some hacks, but they include many pitfalls). > > -Peff > > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: info/exclude not working
On Mon, Jun 03, 2013 at 01:04:39PM -0700, Devin Rhode wrote: > MBP:dish devin$ cat ../.git/info/exclude > # git ls-files --others --exclude-from=.git/info/exclude > # Lines that start with '#' are comments. > # For a project mostly in C, the following would be a good set of > # exclude patterns (uncomment them if you want to use them): > # *.[oa] > # *~ > models/CAFE.json > dish/models/CAFE.json > > MBP:dish devin$ git status > # On branch master > # Changes not staged for commit: > # (use "git add ..." to update what will be committed) > # (use "git checkout -- ..." to discard changes in working directory) > # > # modified: models/CAFE.json ***Shouldn't appear The exclude mechanism does not mean "do not ever look at this file". It means "when you are adding untracked files, do not include this one". Somebody has already added the file to the repository before your exclude was in place, so it is a tracked file. There is currently no official mechanism in git to do what you want (there are some hacks, but they include many pitfalls). -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
info/exclude not working
For some reason info/exclude hasn't been working for me. I have a pretty plain macbook pro, with a slow standard hard drive, running the latest mac os 10.7 lion MBP:dish devin$ pwd /Users/devin/Dropbox/ads-G2/dish MBP:dish devin$ cat ../.git/info/exclude # git ls-files --others --exclude-from=.git/info/exclude # Lines that start with '#' are comments. # For a project mostly in C, the following would be a good set of # exclude patterns (uncomment them if you want to use them): # *.[oa] # *~ models/CAFE.json dish/models/CAFE.json MBP:dish devin$ git status # On branch master # Changes not staged for commit: # (use "git add ..." to update what will be committed) # (use "git checkout -- ..." to discard changes in working directory) # # modified: models/CAFE.json ***Shouldn't appear # modified: page_0.ejs # modified: page_0.xml # modified: page_1.ejs # modified: page_1.xml # no changes added to commit (use "git add" and/or "git commit -a") -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
