Lost the plot – Gone crazy or completely stupid. Cheese Eating Surrender Monkeys – The French. This list is not for the faint of heart and will feature some rather rude language. So, in a bid a further cultural understanding, we’ve decided to put together a list of the most beautiful British insults. One of our favorite facets of British English are the beautiful insults that are possible with the proper turn of phrase. It’s a proven scientific fact that insults are 100x better when they’re spoken with a British accent. Anglotopia’s Grand Adventure – Land’s End to John O’Groats. Great Britons Book: Top 50 Greatest Brits Who Ever Lived. 101 Budget Britain Travel Tips – 2nd Edition. ltimate List of Funny British Place Names. British Slang: Tea Time – British Words for Tea and Tea Related Culture. British Slang: Your Guide to British Police Slang for the Telly Watcher. British English: The Top 50 Most Beautiful British Insults. You have to use git diff HEAD (you may want to add -name-only or similar) to see what, if anything, is different between the work-tree and the HEAD commit unless (as is often the case) the index matches the HEAD commit. What git status tells you is both the answer to "what, if anything, is staged for commit" and "what, if anything, is different between the work-tree and the index". However, it's reasonable to ask separately whether the index is clean (i.e., there is nothing staged for commit) and/or the work-tree is clean (unchanged) with respect to fill-in-the-blank, where the blank can be filled in with "the staging area" or "the HEAD commit". The "right" definition is, I think, that your tree is "clean" if there are no changes to commit and no changes between "tree staged for commit" (contents of index) and "work directory". No, in fact, it makes the working directory clean again! This follows from the (lack of) output of git diff HEAD: "un-staging" the change that adds the second line makes the index refer to the HEAD version, and the working-directory version is the same as the HEAD version, so un-staging the "changes to be committed" causes there to be nothing to commit and no working-directory changes. It says we can use git reset (which is the same as git reset -mixed) with HEAD and the file name to un-stage surely that will make the working directory dirty? :-) $ git reset HEAD file " to discard changes in working directory) This time let's use the long form of git status so that it gives us more information: $ echo second line > file git add file echo contents > file Let's put that odd change back and do one more thing. 
Nothing to commit, working directory clean Both git diff and git diff -cached show changes (so yes, it's "dirty"), but git diff HEAD says there's no change, and if we git add it again and try git status: $ git status -short
Is file dirty? Well, git status -short says that it is, twice (two Ms). But the work-tree version of file has just the one line in it, and matches what's in the repository. $ echo second line > file git add file echo contents > fileĪt this point, the index has file with two lines in it. We now have a repository with one commit containing one file. Initialized empty Git repository in /tmp/repo/.git/ I think the "best answer" is that both are wrong, although the former (the version) is probably closer.Ĭonsider: $ mkdir /tmp/repo & cd /tmp/repo
0 kommentar(er)
