{"thread":{"id":"1013","subject":"Re: Updated git HOWTO for kernel hackers","startedAt":"2005-06-23T14:31:57Z","lastAt":"2005-10-01T00:17:25Z","messageCount":3,"participants":["Horst von Brand","Jeff Garzik"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"5184","messageId":"200506231431.j5NEVvpK004472@laptop11.inf.utfsm.cl","threadId":"1013","inReplyTo":"jgarzik@pobox.com","subject":"Re: Updated git HOWTO for kernel hackers","fromName":"Horst von Brand","fromEmail":"vonbrand@inf.utfsm.cl","sentAt":"2005-06-23T14:31:57Z","receivedAt":"2005-06-23T14:31:57Z","isPatch":false,"sender":{"key":"vonbrand@inf.utfsm.cl","avatar":"https://avatars.githubusercontent.com/u/211384?v=4"},"body":"Jeff Garzik <jgarzik@pobox.com> said:\n> Linus Torvalds wrote:\n> > \trsync -r --ignore-existing repo/refs/tags/ .git/refs/tags/\n> > \n> > See? What's your complaint with just doing that?\n> \n> No complaint with that operation.  The complaint is that it's an \n> additional operation.  Re-read what Greg said:\n> \n> > Is there some reason why git doesn't pull the\n> > tags in properly when doing a merge?  Chris and I just hit this when I\n> > pulled his 2.6.12.1 tree and and was wondering where the tag went.\n> \n> Multiple users -- not just me -- would prefer that git-pull-script \n> pulled the tags, too.\n> \n> Suggested solution:  add '--tags' to git-pull-script \n> (git-fetch-script?), which calls\n> \trsync -r --ignore-existing repo/refs/tags/ .git/refs/tags/\n\nI don't think either is really a solution. IMHO there should be a\ndistinction between \"official tags\" (that get passed around together with\neverything else) and \"private tags\" for everybodys own home use (that could\nbe passed around, but only explicitly). Plus the possibility to erase,\nmove, &c private tags, and perhaps upgrade them to official status (thus\nsetting them in stone).\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":"9561","messageId":"200509301813.j8UIDXr5015488@laptop11.inf.utfsm.cl","threadId":"1013","inReplyTo":"jgarzik@pobox.com","subject":"Re: [howto] Kernel hacker's guide to git, updated","fromName":"Horst von Brand","fromEmail":"vonbrand@inf.utfsm.cl","sentAt":"2005-09-30T18:13:33Z","receivedAt":"2005-09-30T18:13:33Z","isPatch":false,"sender":{"key":"vonbrand@inf.utfsm.cl","avatar":"https://avatars.githubusercontent.com/u/211384?v=4"},"body":"Jeff Garzik <jgarzik@pobox.com> wrote:\n> Thanks for all the comments.  I just updated the KHGtG with the\n> feedback I received.  Go to\n> \n> \thttp://linux.yyz.us/git-howto.html\n> \n> and click reload.  Continued criticism^H^H^Hcomments welcome!\n\n- To know the current branch, \"git branch\" is enough (the one '*'-ed)\n- rsync(1) a repository is dangerous, it might catch it in the middle of\n  a update and give you an incomplete/messed up copy. Repeat rsync until no\n  change, perhaps?\n- I understand \"git checkout -f\" blows away any local changes, no questions\n  asked. Not very nice to suggest that to a newbie...\n\nThanks for the docu!\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":"9573","messageId":"433DD595.4070508@pobox.com","threadId":"1013","inReplyTo":"200509301813.j8UIDXr5015488@laptop11.inf.utfsm.cl","subject":"Re: [howto] Kernel hacker's guide to git, updated","fromName":"Jeff Garzik","fromEmail":"jgarzik@pobox.com","sentAt":"2005-10-01T00:17:25Z","receivedAt":"2005-10-01T00:17:25Z","isPatch":false,"sender":{"key":"jgarzik@pobox.com","avatar":null},"body":"Horst von Brand wrote:\n> Jeff Garzik <jgarzik@pobox.com> wrote:\n> \n>>Thanks for all the comments.  I just updated the KHGtG with the\n>>feedback I received.  Go to\n>>\n>>\thttp://linux.yyz.us/git-howto.html\n>>\n>>and click reload.  Continued criticism^H^H^Hcomments welcome!\n> \n> \n> - To know the current branch, \"git branch\" is enough (the one '*'-ed)\n\nClick reload, this is already mentioned.\n\n\n> - rsync(1) a repository is dangerous, it might catch it in the middle of\n>   a update and give you an incomplete/messed up copy. Repeat rsync until no\n>   change, perhaps?\n\nUsually that's just unlucky.  I have caught kernel.org in the middle of \na sync once, maybe twice.\n\n\n> - I understand \"git checkout -f\" blows away any local changes, no questions\n>   asked. Not very nice to suggest that to a newbie...\n\nI constantly run into problems if I -do not- use the \"-f\" flag.  I \nhabitually use it at all times, now.\n\nThanks,\n\n\tJeff\n"}]}