[git-users] Re: does git smart http use gzip?
can u send me autopilot code please --
Re: [git-users] error changes not staged for commit (windows)
Is it in your .gitignore file? Wes On Mon, Nov 26, 2012 at 9:34 AM, git-guy douglasdeod...@gmail.com wrote: i had tried git add . git add path file but still no add the files, some help what happening? should add with git add . but i dont know what happening #git status # On branch master #Your branch is ahead of 'origin/master' by 1 commit # Changes not staged for commit: # (use git add file... to update what will be committed) # (use git checkout -- file... to discard changes in working directory) # # deleted: templates/file.txt # deleted: templates/test.jsp # no changes added to commit (use git add and/or git commit -a) -- --
Re: [git-users] error changes not staged for commit (windows)
hi william that working, but i dont know because in mac doesn't matter if i delete but command line or no, if i am write add . git will add the file deleted or no and i will commit. something change in git these last monts, or that because i using windows? thanks. On 26 November 2012 14:39, William Mizuta william.miz...@gmail.com wrote: If you want to delete a file, use git rm instead of git add. William Seiti Mizuta @williammizuta Desenvolvedor da Caelum On Mon, Nov 26, 2012 at 12:35 PM, Wes Freeman freeman@gmail.comwrote: Is it in your .gitignore file? Wes On Mon, Nov 26, 2012 at 9:34 AM, git-guy douglasdeod...@gmail.comwrote: i had tried git add . git add path file but still no add the files, some help what happening? should add with git add . but i dont know what happening #git status # On branch master #Your branch is ahead of 'origin/master' by 1 commit # Changes not staged for commit: # (use git add file... to update what will be committed) # (use git checkout -- file... to discard changes in working directory) # # deleted: templates/file.txt # deleted: templates/test.jsp # no changes added to commit (use git add and/or git commit -a) -- -- -- -- Cheers! Douglas Deodato | douglasdeodato.com Portfolio: http://bit.ly/fyXHnw “Choose a job you love, and you will never have to work a day in your life.” Confucios(504 B.C.) --
[git-users] permanent branch deletion on origin
I've done a cvs2git conversion of a number of cvs modules and was unable to exclude the private working branches, PWB*. I'd like to delete them from the git repos and have tried the following, but the branches live on regardless of the output messages. By that I mean if I clone another instance of test, the branches still show up on the origin server. mkdir test cd test git clone git@git:/git/gitroot/oacis/test cd test git branch -r | grep PWB origin/PWB1 origin/PWB10 origin/PWB2 origin/PWB3 origin/PWB4 origin/PWB5 origin/PWB6 origin/PWB7 origin/PWB8 origin/PWB9 for i in `git branch -r | grep PWB`;do git branch -rD $i;done Deleted remote branch origin/PWB1 (was 4e34650). Deleted remote branch origin/PWB10 (was 2992912). Deleted remote branch origin/PWB2 (was b9126e8). Deleted remote branch origin/PWB3 (was e48d2d1). Deleted remote branch origin/PWB4 (was 32c90f3). Deleted remote branch origin/PWB5 (was 234f826). Deleted remote branch origin/PWB6 (was 72409ca). Deleted remote branch origin/PWB7 (was 234f826). Deleted remote branch origin/PWB8 (was e30b526). Deleted remote branch origin/PWB9 (was a8ab921). --
Re: [git-users] permanent branch deletion on origin
I think that git branch -rD only deletes the local reference to remote branches. If you want to delete the branch in your remote repository, for example PWB1, type git push origin :PWB1 William Seiti Mizuta @williammizuta Desenvolvedor da Caelum On Mon, Nov 26, 2012 at 1:06 PM, Jeffrey Marans jmar...@gmail.com wrote: I've done a cvs2git conversion of a number of cvs modules and was unable to exclude the private working branches, PWB*. I'd like to delete them from the git repos and have tried the following, but the branches live on regardless of the output messages. By that I mean if I clone another instance of test, the branches still show up on the origin server. mkdir test cd test git clone git@git:/git/gitroot/oacis/test cd test git branch -r | grep PWB origin/PWB1 origin/PWB10 origin/PWB2 origin/PWB3 origin/PWB4 origin/PWB5 origin/PWB6 origin/PWB7 origin/PWB8 origin/PWB9 for i in `git branch -r | grep PWB`;do git branch -rD $i;done Deleted remote branch origin/PWB1 (was 4e34650). Deleted remote branch origin/PWB10 (was 2992912). Deleted remote branch origin/PWB2 (was b9126e8). Deleted remote branch origin/PWB3 (was e48d2d1). Deleted remote branch origin/PWB4 (was 32c90f3). Deleted remote branch origin/PWB5 (was 234f826). Deleted remote branch origin/PWB6 (was 72409ca). Deleted remote branch origin/PWB7 (was 234f826). Deleted remote branch origin/PWB8 (was e30b526). Deleted remote branch origin/PWB9 (was a8ab921). -- --
Re: [git-users] permanent branch deletion on origin
you can use git push remote branch_local:branch_remote that push in remote your local branch branch_local into the remote branch branch_remote if you want to delete a branch in remote, you can do this: git push remote : branch_remote it's like to say: please, copy nothing from my local to branch_remote , and voila, deleted Bye! -Joe 2012/11/26 William Mizuta william.miz...@gmail.com I think that git branch -rD only deletes the local reference to remote branches. If you want to delete the branch in your remote repository, for example PWB1, type git push origin :PWB1 William Seiti Mizuta @williammizuta Desenvolvedor da Caelum On Mon, Nov 26, 2012 at 1:06 PM, Jeffrey Marans jmar...@gmail.com wrote: I've done a cvs2git conversion of a number of cvs modules and was unable to exclude the private working branches, PWB*. I'd like to delete them from the git repos and have tried the following, but the branches live on regardless of the output messages. By that I mean if I clone another instance of test, the branches still show up on the origin server. mkdir test cd test git clone git@git:/git/gitroot/oacis/test cd test git branch -r | grep PWB origin/PWB1 origin/PWB10 origin/PWB2 origin/PWB3 origin/PWB4 origin/PWB5 origin/PWB6 origin/PWB7 origin/PWB8 origin/PWB9 for i in `git branch -r | grep PWB`;do git branch -rD $i;done Deleted remote branch origin/PWB1 (was 4e34650). Deleted remote branch origin/PWB10 (was 2992912). Deleted remote branch origin/PWB2 (was b9126e8). Deleted remote branch origin/PWB3 (was e48d2d1). Deleted remote branch origin/PWB4 (was 32c90f3). Deleted remote branch origin/PWB5 (was 234f826). Deleted remote branch origin/PWB6 (was 72409ca). Deleted remote branch origin/PWB7 (was 234f826). Deleted remote branch origin/PWB8 (was e30b526). Deleted remote branch origin/PWB9 (was a8ab921). -- -- --
Re: [git-users] permanent branch deletion on origin
On Mon, 26 Nov 2012 07:06:35 -0800 (PST) Jeffrey Marans jmar...@gmail.com wrote: I've done a cvs2git conversion of a number of cvs modules and was unable to exclude the private working branches, PWB*. I'd like to delete them from the git repos and have tried the following, but the branches live on regardless of the output messages. By that I mean if I clone another instance of test, the branches still show up on the origin server. mkdir test cd test git clone git@git:/git/gitroot/oacis/test cd test git branch -r | grep PWB [...] origin/PWB9 for i in `git branch -r | grep PWB`;do git branch -rD $i;done [...] Deleted remote branch origin/PWB9 (was a8ab921). You misunderstand what those origin/foo branches are. Unfortunately, the naming of these things adopted by Git just adds to the confusion (though I don't think they could do it any better). Those branches *in your local repository* (which are not shown by a call to `git branch` without the -r command-line option) are the so-called remote branches. They capture the state of the branches the corresponding remote repository had the last time you did `git fetch` from that repo. They exist only in your repo, as a reference, and deleting them (or renaming or whatnot) does not affect any remote repository in any way. They are like bookmarks. They exists to provide convenient handles to remote history, but in the same way as removing a bookmark from a book does not affect a book, removing a remote branch from your local repository does not even hits the network and modifies only your local repository. The next `git fetch origin` will (re-)create these branches. To delete something from a remote repo you have to use a somewhat obscure (on the first sight) feature of the `git push` command -- you should push *nothing* to a named remote object (a branch in your case). The idea goes like this: the full syntax to update a branch named master in the remote repo with the contents of your local branch named master is spelled as $ git push origin master:master Git allows you to drop the remote object specification -- the :master part -- in which case it's assumed the remote object will have the same name and type, so when you do $ git push origin master Git takes your local object master (be it a branch or a tag -- it does not matter) and tries to update a same-named object in the remote repo, creating it if necessary. If you want to delete an object from a remote repo, you push nothing to it -- using the full syntax: $ git push origin :master means updating an object named master in the remote repo with nothing, thus deleting it. So to delete a branch named PWB9 from origin you should do $ git push origin :PWB9 You could also employ the fact Git is able to use wildcards for both local and remote objects, so you could possibly do $ git push origin ':refs/heads/PWB*' where you tell it to remote all heads (branches) matching the PWB* pattern. Be sure to protect the pattern from the shell, if needed. As usually, this syntax is explained in the `git push` manual page. And in The Book [1] as well. 1. http://git-scm.com/book/en/Git-Branching-Remote-Branches --
[git-users] exclude a subdirectory in sparse-checkout
Hi all, I'm trying to exclude a new subdirectory that was added by someone else. in my $GITDIR/info/sparse-checkout file, I have: /web/ Now, I want to exclude the /web/tests/ subdirectory. So I changed my file to: /web/ !/web/tests/ but this does not work. After calling git read-tree -m -u HEAD the subdirectory /web/tests is still present. If I change to: /web/ !tests the /web/tests subdirectory does disappear, but this may exclude possible 'tests' directory under any other subdirectories that I may want to keep. Is it possible to do what I want? Thanks. H. --
Re: [git-users] exclude a subdirectory in sparse-checkout
Try to use git rm -r /web/tests to remove the directory from your git project. William Seiti Mizuta @williammizuta Desenvolvedor da Caelum On Mon, Nov 26, 2012 at 2:18 PM, Huu Da Tran huuda.t...@gmail.com wrote: Hi all, I'm trying to exclude a new subdirectory that was added by someone else. in my $GITDIR/info/sparse-checkout file, I have: /web/ Now, I want to exclude the /web/tests/ subdirectory. So I changed my file to: /web/ !/web/tests/ but this does not work. After calling git read-tree -m -u HEAD the subdirectory /web/tests is still present. If I change to: /web/ !tests the /web/tests subdirectory does disappear, but this may exclude possible 'tests' directory under any other subdirectories that I may want to keep. Is it possible to do what I want? Thanks. H. -- --
[git-users] deletion of git object?
OK, this is more a question to help me understand git internals than an actual problem that I am having. But suppose I create a new branch. git checkout -b newbranch. I am now in the newbranch branch. So I create a new file in my working directory such as: date ldate. I now have ldate in my working directory. I do: git add ldate and git commit -m 'added ldate to track last date'. The contents of ldate are kept in a git object whose name is the sha1sum of the contents. I now decide this is silly. So I want to eliminate newbranch. The simpliest way, not having done a git push is to just kill it with git branch master;git branch -D newbranch. Now, after this, is the git object for the now non-existent ldate file already cleaned up? Or do I need to do something else, such as git gc, git prune? I'm pretty sure that the git gc is the best bet. --
Re: [git-users] exclude a subdirectory in sparse-checkout
On Monday, November 26, 2012 12:42:55 PM UTC-5, William Mizuta wrote: Try to use git rm -r /web/tests to remove the directory from your git project. I want to keep it in the repo, but not in the sparse-checkout. Sorry if that was not clear in my original question. Thanks. H. --
Re: [git-users] deletion of git object?
As far as I know about git, these objects are not deleted. And not only the file, but also the objects that represent the tree and commit. You can check this using git fsck --full. This command will find dangling objects and you can see its content using git cat-file -p sha1sum. If you want to delete these dangling objects, you should use git gc --prune. It will delete dangling objects that are older than a certain time. The default value is two weeks, however you can change this value. I hope that it helped you. William Seiti Mizuta @williammizuta Desenvolvedor da Caelum On Mon, Nov 26, 2012 at 4:07 PM, John McKown john.archie.mck...@gmail.comwrote: OK, this is more a question to help me understand git internals than an actual problem that I am having. But suppose I create a new branch. git checkout -b newbranch. I am now in the newbranch branch. So I create a new file in my working directory such as: date ldate. I now have ldate in my working directory. I do: git add ldate and git commit -m 'added ldate to track last date'. The contents of ldate are kept in a git object whose name is the sha1sum of the contents. I now decide this is silly. So I want to eliminate newbranch. The simpliest way, not having done a git push is to just kill it with git branch master;git branch -D newbranch. Now, after this, is the git object for the now non-existent ldate file already cleaned up? Or do I need to do something else, such as git gc, git prune? I'm pretty sure that the git gc is the best bet. -- --
Re: [git-users] deletion of git object?
From: John McKown To: git-users@googlegroups.com Sent: Monday, November 26, 2012 6:07 PM Subject: [git-users] deletion of git object? OK, this is more a question to help me understand git internals than an actual problem that I am having. But suppose I create a new branch. git checkout -b newbranch. I am now in the newbranch branch. So I create a new file in my working directory such as: date ldate. I now have ldate in my working directory. I do: git add ldate and git commit -m 'added ldate to track last date'. The contents of ldate are kept in a git object whose name is the sha1sum of the contents. I now decide this is silly. So I want to eliminate newbranch. The simpliest way, not having done a git push is to just kill it with git branch master;git branch -D newbranch. Now, after this, is the git object for the now non-existent ldate file already cleaned up? Or do I need to do something else, such as git gc, git prune? I'm pretty sure that the git gc is the best bet. -- John, The objects are still there for a while. There is I believe an automatic cleanup after, IIRC 30 days, that cleans the logs, reflogs and other loose items that are no longer referenced [1]. There are even 'lost and found' methods should the worst happen and you need to find a dropped object. I think (but don't quote me) that the branch creation / deletion log is now enabled by default so it should be possible to immediately recover the deleted branch. There is usually no need to do a special 'git gc' (garbage collection), but old habits . Philip [1] it could be that it is the git gc auto that ensures the 30 days .. I just let the tools do their thing ;-) --
[git-users] Nice book review about git
This is on Version Control With Git, 2nd Edition. I read the review and decided to get the Kindle version of the book for just under US $16.00 . But the Kindle is at home, so I can't look at it right now. I've just about finished up Pro Git and liked it. I am a bit off in the head, in that I like to read well written computer documentation. OK, maybe some other ways too. grin/ http://books.slashdot.org/story/12/11/26/1330226/book-review-version-control-with-git-2nd-edition --
Re: [git-users] error changes not staged for commit (windows)
On linux, if I forget to use `git rm` to delete a file, I can remove the file from the index using `git add -u`. Note that it will also stage any other modifications to the exiting files in the working tree along with removing the deleted files from index. Regards, Vineet On Mon, Nov 26, 2012 at 8:16 PM, Douglas Deodato douglasdeod...@gmail.com wrote: hi william that working, but i dont know because in mac doesn't matter if i delete but command line or no, if i am write add . git will add the file deleted or no and i will commit. something change in git these last monts, or that because i using windows? thanks. On 26 November 2012 14:39, William Mizuta william.miz...@gmail.com wrote: If you want to delete a file, use git rm instead of git add. William Seiti Mizuta @williammizuta Desenvolvedor da Caelum On Mon, Nov 26, 2012 at 12:35 PM, Wes Freeman freeman@gmail.com wrote: Is it in your .gitignore file? Wes On Mon, Nov 26, 2012 at 9:34 AM, git-guy douglasdeod...@gmail.com wrote: i had tried git add . git add path file but still no add the files, some help what happening? should add with git add . but i dont know what happening #git status # On branch master #Your branch is ahead of 'origin/master' by 1 commit # Changes not staged for commit: # (use git add file... to update what will be committed) # (use git checkout -- file... to discard changes in working directory) # # deleted: templates/file.txt # deleted: templates/test.jsp # no changes added to commit (use git add and/or git commit -a) -- -- -- -- Cheers! Douglas Deodato | douglasdeodato.com Portfolio: http://bit.ly/fyXHnw “Choose a job you love, and you will never have to work a day in your life.” Confucios(504 B.C.) -- -- Vineet Naik --
