{"thread":{"id":"2150","subject":"Re: Pushing a single tag (ref + object)?","startedAt":"2005-10-19T12:39:05Z","lastAt":"2005-11-02T09:26:59Z","messageCount":4,"participants":["Horst von Brand","Andreas Ericsson","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"10279","messageId":"200510191239.j9JCd5nQ018754@laptop11.inf.utfsm.cl","threadId":"2150","inReplyTo":"martin.langhoff@gmail.com","subject":"Re: Pushing a single tag (ref + object)?","fromName":"Horst von Brand","fromEmail":"vonbrand@inf.utfsm.cl","sentAt":"2005-10-19T12:39:05Z","receivedAt":"2005-10-19T12:39:05Z","isPatch":false,"sender":{"key":"vonbrand@inf.utfsm.cl","avatar":"https://avatars.githubusercontent.com/u/211384?v=4"},"body":"Martin Langhoff wrote:\n> While we are using a repo which holds all our branches\n> (dev/test/prod), locally we have a group of developers that checkout\n> one repo-per-branch, working on it with a\n> cg-clone/cg-update/cg-commit/cg-push workcycle. So far it's working\n> great.\n> \n> Now, I am at a loss on how to push a _tag_ object+ref to the repo,\n> without doing a git-push --all, which I naturally don't want to do. I\n> managed to push the object itself, doing\n> \n> git-push repository tagrefname\n> \n> But that ddn't create the ref on the repo. So I had to do\n> \n> scp .git/refs/tags/refname repostory/refs/tags/\n\nI've done:\n\n git push repository refs/tags/refname\n-- \nDr. Horst H. von Brand User #22616 counter.li.org\nDepartamento de Informatica Fono: +56 32 654431\nUniversidad Tecnica Federico Santa Maria +56 32 654239\nCasilla 110-V, Valparaiso, Chile Fax: +56 32 797513\n"},{"id":"10986","messageId":"200511012356.jA1NuPBd004502@inti.inf.utfsm.cl","threadId":"2150","inReplyTo":"martin.langhoff@gmail.com","subject":"Re: git versus CVS (versus bk)","fromName":"Horst von Brand","fromEmail":"vonbrand@inf.utfsm.cl","sentAt":"2005-11-01T23:56:25Z","receivedAt":"2005-11-01T23:56:25Z","isPatch":false,"sender":{"key":"vonbrand@inf.utfsm.cl","avatar":"https://avatars.githubusercontent.com/u/211384?v=4"},"body":"Martin Langhoff wrote:\n\n[...]\n\n> In practice, a new developer will often roll up commits to avoid\n> sending a string of shameful patches and corrections on top -- I often\n> do that ;-) . Developers with more \"mana\" will have published repos\n> where Junio pulls directly from -- and they get merged with full\n> history. Of course -- they don't have brown-paper-bag commits like I\n> do...\n\nI bet they have a scratchpad on their laptop (full of brown-paper-bag\ncommits and backtracking) from which they push into a cleaned up repository\nfor public consumption.\n-- \nDr. Horst H. von Brand User #22616 counter.li.org\nDepartamento de Informatica Fono: +56 32 654431\nUniversidad Tecnica Federico Santa Maria +56 32 654239\nCasilla 110-V, Valparaiso, Chile Fax: +56 32 797513\n"},{"id":"11003","messageId":"43687EAF.4060505@op5.se","threadId":"2150","inReplyTo":"200511012356.jA1NuPBd004502@inti.inf.utfsm.cl","subject":"Re: git versus CVS (versus bk)","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2005-11-02T08:54:07Z","receivedAt":"2005-11-02T08:54:07Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Horst von Brand wrote:\n> Martin Langhoff wrote:\n> \n> [...]\n> \n> \n>>In practice, a new developer will often roll up commits to avoid\n>>sending a string of shameful patches and corrections on top -- I often\n>>do that ;-) . Developers with more \"mana\" will have published repos\n>>where Junio pulls directly from -- and they get merged with full\n>>history. Of course -- they don't have brown-paper-bag commits like I\n>>do...\n> \n> \n> I bet they have a scratchpad on their laptop (full of brown-paper-bag\n> commits and backtracking) from which they push into a cleaned up repository\n> for public consumption.\n\nI just do a lot of branches.\n\nIncidentally though, is there any way to make a commit completely go \naway without resetting the files?\n\nIt'd be a nice feature even if it can only do it from the top down, \nunlike git-revert which can do it anywhere in the middle as well.\n\n-- \nAndreas Ericsson andreas.ericsson@op5.se\nOP5 AB www.op5.se\nTel: +46 8-230225 Fax: +46 8-230231\n"},{"id":"11007","messageId":"7v8xw7v1r0.fsf@assigned-by-dhcp.cox.net","threadId":"2150","inReplyTo":"43687EAF.4060505@op5.se","subject":"Re: git versus CVS (versus bk)","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-11-02T09:26:59Z","receivedAt":"2005-11-02T09:26:59Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Andreas Ericsson writes:\n\n> Incidentally though, is there any way to make a commit completely go \n> away without resetting the files?\n\nI am not sure if this is what you are looking for, but after I\nmake a commit and find a mistake (either in the checked-in files\nor commit log message), I do this:\n\n\t$ git reset --soft HEAD^\n ... fix the checked-in files, maybe do git-add files that\n ... I forgot to add when I made the last commit.\n $ git commit -a -c ORIG_HEAD ;# edit commit log, too.\n\nSoft reset leaves the working tree files intact and just rewinds\nthe .git/HEAD to whatever commit you specify, and as a side\neffect stores the original .git/HEAD in .git/ORIG_HEAD. The\nlowercase -c flag to git-commit is \"bring the commit log editor,\ninitialized with the commit log message from that commit\".\n"}]}