{"thread":{"id":"6100","subject":"Re: Updated Kernel Hacker's guide to git","startedAt":"2006-12-24T18:07:04Z","lastAt":"2008-07-03T06:26:59Z","messageCount":19,"participants":["Horst H. von Brand","Jeff Garzik","Robert P. J. Day","WANG Cong","Dieter Ries","Stefan Richter","Miklos Vajna","Salikh Zakirov","Jan Engelhardt","Junio C Hamano","Christian Couder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"30251","messageId":"200612241807.kBOI746w008739@laptop13.inf.utfsm.cl","threadId":"6100","inReplyTo":"jeff@garzik.org","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Horst H. von Brand","fromEmail":"vonbrand@inf.utfsm.cl","sentAt":"2006-12-24T18:07:04Z","receivedAt":"2006-12-24T18:07:04Z","isPatch":false,"sender":{"key":"vonbrand@inf.utfsm.cl","avatar":"https://avatars.githubusercontent.com/u/211384?v=4"},"body":"Jeff Garzik wrote:\n> I refreshed my git intro/cookbook for kernel hackers, at\n> http://linux.yyz.us/git-howto.html\n\nLooks nice, starting to look it over.\n\nNotes:\n\nGetting started:\n\n There are RPM packages available (I think they are for latest Fedora; in\n case of doubt get the latest SRPM and build yourself, sometimes the\n distros lag /way/ behind). There are also Debian packages there, dunno\n about those.\n\nBasic tasks:\n\n 'git pull' should be enough, no need to give the URL each time.\n It is useful to tell people how to get \"nonofficial\" branches (via URL +\n branches) too.\n \n\nMiscellaneous debris:\n\n 'git pull' has gotten tags each time for me?\n-- \nDr. Horst H. von Brand User #22616 counter.li.org\nDepartamento de Informatica Fono: +56 32 2654431\nUniversidad Tecnica Federico Santa Maria +56 32 2654239\nCasilla 110-V, Valparaiso, Chile Fax: +56 32 2797513\n"},{"id":"64034","messageId":"476E42BF.1010300@garzik.org","threadId":"6100","inReplyTo":"200612241807.kBOI746w008739@laptop13.inf.utfsm.cl","subject":"Updated Kernel Hacker's guide to git","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2007-12-23T11:13:03Z","receivedAt":"2007-12-23T11:13:03Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"Another year, another update! :)\n\nThe kernel hacker's guide to git has received some updates:\n\n\thttp://linux.yyz.us/git-howto.html\n\nThis includes all the input sent to me in the past several months, as \nwell as a few new tips and tricks I use on a regular basis.\n\nIn general, this document is designed to be a quick-start cookbook, and \nnot a comprehensive introduction.\n\nMerry Christmas and Happy Holidays to all!\n\n\tJeff\n\n\n\n"},{"id":"64036","messageId":"alpine.LFD.0.9999.0712230701520.14863@localhost.localdomain","threadId":"6100","inReplyTo":"476E42BF.1010300@garzik.org","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Robert P. J. Day","fromEmail":"rpjday@crashcourse.ca","sentAt":"2007-12-23T12:08:37Z","receivedAt":"2007-12-23T12:08:37Z","isPatch":false,"sender":{"key":"rpjday@crashcourse.ca","avatar":"https://avatars.githubusercontent.com/u/226084077?v=4"},"body":"On Sun, 23 Dec 2007, Jeff Garzik wrote:\n\n> Another year, another update! :)\n>\n> The kernel hacker's guide to git has received some updates:\n>\n> \thttp://linux.yyz.us/git-howto.html\n>\n> This includes all the input sent to me in the past several months,\n> as well as a few new tips and tricks I use on a regular basis.\n>\n> In general, this document is designed to be a quick-start cookbook,\n> and not a comprehensive introduction.\n\nthere's one issue i have with this document, and that's that i wish it\nmore carefully distinguished between regular git \"user\" tasks, and git\n\"developer\" tasks.\n\ni may be mistaken, but it would seem that a lot of folks are going to\nbe what i call basic users, who only want to update their git tree,\ncheck the logs, check the status and so on. and if they start to get\nambitious, they might make some changes to the tree, do a diff, and\nsubmit a patch. but in the beginning, they won't be making commits or\nswitching branches, etc.\n\nin short, i can see the value of something like a \"getting started\nwith git as a basic user\" tutorial. does such a thing exist?\n\nrday\n--\n\n========================================================================\nRobert P. J. Day\nLinux Consulting, Training and Annoying Kernel Pedantry\nWaterloo, Ontario, CANADA\n\nhttp://crashcourse.ca\n========================================================================\n"},{"id":"64037","messageId":"476E50DC.1040701@garzik.org","threadId":"6100","inReplyTo":"alpine.LFD.0.9999.0712230701520.14863@localhost.localdomain","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2007-12-23T12:13:16Z","receivedAt":"2007-12-23T12:13:16Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"Robert P. J. Day wrote:\n> On Sun, 23 Dec 2007, Jeff Garzik wrote:\n> \n>> Another year, another update! :)\n>>\n>> The kernel hacker's guide to git has received some updates:\n>>\n>> \thttp://linux.yyz.us/git-howto.html\n>>\n>> This includes all the input sent to me in the past several months,\n>> as well as a few new tips and tricks I use on a regular basis.\n>>\n>> In general, this document is designed to be a quick-start cookbook,\n>> and not a comprehensive introduction.\n> \n> there's one issue i have with this document, and that's that i wish it\n> more carefully distinguished between regular git \"user\" tasks, and git\n> \"developer\" tasks.\n> \n> i may be mistaken, but it would seem that a lot of folks are going to\n> be what i call basic users, who only want to update their git tree,\n> check the logs, check the status and so on. and if they start to get\n> ambitious, they might make some changes to the tree, do a diff, and\n> submit a patch. but in the beginning, they won't be making commits or\n> switching branches, etc.\n> \n> in short, i can see the value of something like a \"getting started\n> with git as a basic user\" tutorial. does such a thing exist?\n\n\nhmmm. There's the tutorial linked at the bottom of the page, which in \nturn links to http://www.kernel.org/pub/software/scm/git/docs/everyday.html\n\ngit is a developer's tool, so I sorta targetted that audience. I \ndefinitely agree that is not only git audience...\n\n\tJeff\n"},{"id":"64038","messageId":"alpine.LFD.0.9999.0712230715490.15596@localhost.localdomain","threadId":"6100","inReplyTo":"476E50DC.1040701@garzik.org","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Robert P. J. Day","fromEmail":"rpjday@crashcourse.ca","sentAt":"2007-12-23T12:20:51Z","receivedAt":"2007-12-23T12:20:51Z","isPatch":false,"sender":{"key":"rpjday@crashcourse.ca","avatar":"https://avatars.githubusercontent.com/u/226084077?v=4"},"body":"On Sun, 23 Dec 2007, Jeff Garzik wrote:\n\n> Robert P. J. Day wrote:\n> > On Sun, 23 Dec 2007, Jeff Garzik wrote:\n> >\n> > > Another year, another update! :)\n> > >\n> > > The kernel hacker's guide to git has received some updates:\n> > >\n> > > \thttp://linux.yyz.us/git-howto.html\n> > >\n> > > This includes all the input sent to me in the past several months,\n> > > as well as a few new tips and tricks I use on a regular basis.\n> > >\n> > > In general, this document is designed to be a quick-start cookbook,\n> > > and not a comprehensive introduction.\n> >\n> > there's one issue i have with this document, and that's that i wish it\n> > more carefully distinguished between regular git \"user\" tasks, and git\n> > \"developer\" tasks.\n> >\n> > i may be mistaken, but it would seem that a lot of folks are going to\n> > be what i call basic users, who only want to update their git tree,\n> > check the logs, check the status and so on. and if they start to get\n> > ambitious, they might make some changes to the tree, do a diff, and\n> > submit a patch. but in the beginning, they won't be making commits or\n> > switching branches, etc.\n> >\n> > in short, i can see the value of something like a \"getting started\n> > with git as a basic user\" tutorial. does such a thing exist?\n>\n> hmmm. There's the tutorial linked at the bottom of the page, which\n> in turn links to\n> http://www.kernel.org/pub/software/scm/git/docs/everyday.html\n>\n> git is a developer's tool, so I sorta targetted that audience. I\n> definitely agree that is not only git audience...\n\njust to be clear, i'm not complaining about the quality of the\ndocument above, but when i got started with git, what i really wanted\nwas a list of what i (as a simple, non-developer user) could do once i\ncloned a repository.\n\nto that end, i put together my own little reference list of git\ncommands. for example, i collected ways to examine my repository --\ngit commands like branch, tag, log/shortlog, what-changed, show, grep,\nblame, that sort of thing. exactly the kind of stuff a new user might\nwant to know about, even without the ability to change anything.\n\njust my $0.02.\n\nrday\n--\n\n========================================================================\nRobert P. J. Day\nLinux Consulting, Training and Annoying Kernel Pedantry\nWaterloo, Ontario, CANADA\n\nhttp://crashcourse.ca\n========================================================================\n"},{"id":"64039","messageId":"20071223122526.GE2462@hacking","threadId":"6100","inReplyTo":"476E42BF.1010300@garzik.org","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"WANG Cong","fromEmail":"xiyou.wangcong@gmail.com","sentAt":"2007-12-23T12:25:26Z","receivedAt":"2007-12-23T12:25:26Z","isPatch":false,"sender":{"key":"xiyou.wangcong@gmail.com","avatar":null},"body":"On Sun, Dec 23, 2007 at 06:13:03AM -0500, Jeff Garzik wrote:\n>Another year, another update! :)\n>\n>The kernel hacker's guide to git has received some updates:\n>\n>\thttp://linux.yyz.us/git-howto.html\n>\n>This includes all the input sent to me in the past several months, as \n>well as a few new tips and tricks I use on a regular basis.\n>\n>In general, this document is designed to be a quick-start cookbook, and \n>not a comprehensive introduction.\n\n\nJeff, very good! I like it. Thank you! ;-)\n\n>\n>Merry Christmas and Happy Holidays to all!\n>\n\nMerry Christmas, kernel hackers!\n\nBest wishes!\n"},{"id":"64040","messageId":"476E5CFC.5070301@gmx.de","threadId":"6100","inReplyTo":"alpine.LFD.0.9999.0712230715490.15596@localhost.localdomain","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Dieter Ries","fromEmail":"clip3@gmx.de","sentAt":"2007-12-23T13:05:00Z","receivedAt":"2007-12-23T13:05:00Z","isPatch":false,"sender":{"key":"clip3@gmx.de","avatar":null},"body":"Robert P. J. Day schrieb:\n> On Sun, 23 Dec 2007, Jeff Garzik wrote:\n> \n>> Robert P. J. Day wrote:\n>>> On Sun, 23 Dec 2007, Jeff Garzik wrote:\n>>>\n>>>> Another year, another update! :)\n>>>>\n>>>> The kernel hacker's guide to git has received some updates:\n>>>>\n>>>> \thttp://linux.yyz.us/git-howto.html\n>>>>\n>>>> This includes all the input sent to me in the past several months,\n>>>> as well as a few new tips and tricks I use on a regular basis.\n>>>>\n>>>> In general, this document is designed to be a quick-start cookbook,\n>>>> and not a comprehensive introduction.\n>>> there's one issue i have with this document, and that's that i wish it\n>>> more carefully distinguished between regular git \"user\" tasks, and git\n>>> \"developer\" tasks.\n>>>\n>>> i may be mistaken, but it would seem that a lot of folks are going to\n>>> be what i call basic users, who only want to update their git tree,\n>>> check the logs, check the status and so on. and if they start to get\n>>> ambitious, they might make some changes to the tree, do a diff, and\n>>> submit a patch. but in the beginning, they won't be making commits or\n>>> switching branches, etc.\n>>>\n>>> in short, i can see the value of something like a \"getting started\n>>> with git as a basic user\" tutorial. does such a thing exist?\n>> hmmm. There's the tutorial linked at the bottom of the page, which\n>> in turn links to\n>> http://www.kernel.org/pub/software/scm/git/docs/everyday.html\n>>\n>> git is a developer's tool, so I sorta targetted that audience. I\n>> definitely agree that is not only git audience...\n> \n> just to be clear, i'm not complaining about the quality of the\n> document above, but when i got started with git, what i really wanted\n> was a list of what i (as a simple, non-developer user) could do once i\n> cloned a repository.\n> \n> to that end, i put together my own little reference list of git\n> commands. for example, i collected ways to examine my repository --\n> git commands like branch, tag, log/shortlog, what-changed, show, grep,\n> blame, that sort of thing. exactly the kind of stuff a new user might\n> want to know about, even without the ability to change anything.\n\nCould you perhaps publish your reference list as kind of a christmas\ngift to all basic users like me?\n\n\ncu\nDieter\n\nps.: sorry for sending this twice, messed up recipients.\n> \n> just my $0.02.\n> \n> rday\n> --\n> \n> ========================================================================\n> Robert P. J. Day\n> Linux Consulting, Training and Annoying Kernel Pedantry\n> Waterloo, Ontario, CANADA\n> \n> http://crashcourse.ca\n> ========================================================================\n> --\n> To unsubscribe from this list: send the line \"unsubscribe linux-kernel\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\n> Please read the FAQ at http://www.tux.org/lkml/\n> \n\n"},{"id":"64048","messageId":"alpine.LFD.0.9999.0712231222370.29681@localhost.localdomain","threadId":"6100","inReplyTo":"476E5CFC.5070301@gmx.de","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Robert P. J. Day","fromEmail":"rpjday@crashcourse.ca","sentAt":"2007-12-23T17:23:39Z","receivedAt":"2007-12-23T17:23:39Z","isPatch":false,"sender":{"key":"rpjday@crashcourse.ca","avatar":"https://avatars.githubusercontent.com/u/226084077?v=4"},"body":"On Sun, 23 Dec 2007, Dieter Ries wrote:\n\n> Robert P. J. Day schrieb:\n\n> > just to be clear, i'm not complaining about the quality of the\n> > document above, but when i got started with git, what i really\n> > wanted was a list of what i (as a simple, non-developer user)\n> > could do once i cloned a repository.\n> >\n> > to that end, i put together my own little reference list of git\n> > commands. for example, i collected ways to examine my repository\n> > -- git commands like branch, tag, log/shortlog, what-changed,\n> > show, grep, blame, that sort of thing. exactly the kind of stuff\n> > a new user might want to know about, even without the ability to\n> > change anything.\n>\n> Could you perhaps publish your reference list as kind of a christmas\n> gift to all basic users like me?\n\nif you give me a day or two (or three), i may put an updated version\nof that up on my wiki.\n\nrday\n\n========================================================================\nRobert P. J. Day\nLinux Consulting, Training and Annoying Kernel Pedantry\nWaterloo, Ontario, CANADA\n\nhttp://crashcourse.ca\n========================================================================\n"},{"id":"64057","messageId":"476EC18B.6080808@s5r6.in-berlin.de","threadId":"6100","inReplyTo":"476E5CFC.5070301@gmx.de","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Stefan Richter","fromEmail":"stefanr@s5r6.in-berlin.de","sentAt":"2007-12-23T20:14:03Z","receivedAt":"2007-12-23T20:14:03Z","isPatch":false,"sender":{"key":"stefanr@s5r6.in-berlin.de","avatar":null},"body":"Dieter Ries wrote:\n> Robert P. J. Day schrieb:\n>> when i got started with git, what i really wanted\n>> was a list of what i (as a simple, non-developer user) could do once i\n>> cloned a repository.\n>>\n>> to that end, i put together my own little reference list of git\n>> commands. for example, i collected ways to examine my repository --\n>> git commands like branch, tag, log/shortlog, what-changed, show, grep,\n>> blame, that sort of thing. exactly the kind of stuff a new user might\n>> want to know about, even without the ability to change anything.\n> \n> Could you perhaps publish your reference list as kind of a christmas\n> gift to all basic users like me?\n\nHere are three out of four things which I do frequently with git repos:\nI look at\n\n - commits and blobs in other people's trees with gitweb,\n\n - commits in a local tree with gitk,\n\n - specific changes to source code with qgit, using it as \"git blame\"\n GUI.\n\n(The fourth thing is feeding a driver subsystem git tree at kernel.org\nusing a minimum number of git commands. Everything else which I do with\ngit I do so infrequently that I have to reread manuals all the time.)\n-- \nStefan Richter\n-=====-=-=== ==-- =-===\nhttp://arcgraph.de/sr/\n"},{"id":"64074","messageId":"20071224125055.GC23659@genesis.frugalware.org","threadId":"6100","inReplyTo":"476E42BF.1010300@garzik.org","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-12-24T12:50:55Z","receivedAt":"2007-12-24T12:50:55Z","isPatch":false,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Sun, Dec 23, 2007 at 06:13:03AM -0500, Jeff Garzik wrote:\n> Another year, another update! :)\n> \n> The kernel hacker's guide to git has received some updates:\n> \n> \thttp://linux.yyz.us/git-howto.html\n\none minor note:\n\ni would suggest using:\n\n$ git shortlog master..HEAD\n\ninstead of\n\n$ git log master..HEAD | git shortlog\n\nto avoid unnecessary complexity :)\n\nthanks,\n- VMiklos\n"},{"id":"64075","messageId":"alpine.LFD.0.9999.0712240918440.17591@localhost.localdomain","threadId":"6100","inReplyTo":"476E5CFC.5070301@gmx.de","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Robert P. J. Day","fromEmail":"rpjday@crashcourse.ca","sentAt":"2007-12-24T14:19:57Z","receivedAt":"2007-12-24T14:19:57Z","isPatch":false,"sender":{"key":"rpjday@crashcourse.ca","avatar":"https://avatars.githubusercontent.com/u/226084077?v=4"},"body":"On Sun, 23 Dec 2007, Dieter Ries wrote:\n\n> Could you perhaps publish your reference list as kind of a christmas\n> gift to all basic users like me?\n\nFYI, i'm typing in my own reference list as we speak here:\n\n http://www.crashcourse.ca/wiki/index.php/Git\n\nstill quite a bit to go, but you can get the overall idea. new\nsections should be appearing there as the morning progresses.\n\nrday\n\n========================================================================\nRobert P. J. Day\nLinux Consulting, Training and Annoying Kernel Pedantry\nWaterloo, Ontario, CANADA\n\nhttp://crashcourse.ca\n========================================================================\n"},{"id":"64093","messageId":"477100BB.6020301@gmail.com","threadId":"6100","inReplyTo":"476E42BF.1010300@garzik.org","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Salikh Zakirov","fromEmail":"salikh@gmail.com","sentAt":"2007-12-25T13:08:11Z","receivedAt":"2007-12-25T13:08:11Z","isPatch":false,"sender":{"key":"salikh@gmail.com","avatar":"https://gravatar.com/avatar/952c102bb1dcf721dab8de4f5a11d276756a65d301d021f755e265cc3251efae?d=mp&s=160"},"body":"Jeff Garzik wrote:\n> The kernel hacker's guide to git has received some updates: \n> http://linux.yyz.us/git-howto.html\n\nI have some comments on the contents, though I need to warn, \nthat I've been following git development for about year and a half now,\nand I am not a kernel hacker, so my comments may have wrong bias.\n\n> Obtain a diff between current branch, and master branch\n> \n> In most trees with branches, .git/refs/heads/master contains the\n> current 'vanilla' upstream tree, for easy diffing and merging. (in\n> trees without branches, 'master' simply contains your latest changes)\n> \n> $ git diff master..HEAD\n\nIMHO, syntax 'git diff master HEAD' is preferable, in order to avoid\nconfusion with 'git log master..HEAD' usage, which has quite different\nmeaning, roughly expressible as\n\n git diff `git merge-base master HEAD` HEAD\n\nfor getting one big diff of the changes in HEAD since master)\n\n> (this is equivalent to git diff HEAD, when used with HEAD branch)\n\nThis seems incorrect to me, as 'git diff master HEAD' compares two\nrevisions, while 'git diff HEAD' compares working tree with HEAD revision.\n\nBesides, expression 'HEAD branch' is misleading, because HEAD is not a branch by itself,\nbut rather a link to the latest state of the current branch.\n"},{"id":"64243","messageId":"Pine.LNX.4.64.0712310349260.2093@fbirervta.pbzchgretzou.qr","threadId":"6100","inReplyTo":"476E42BF.1010300@garzik.org","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Jan Engelhardt","fromEmail":"jengelh@computergmbh.de","sentAt":"2007-12-31T02:50:22Z","receivedAt":"2007-12-31T02:50:22Z","isPatch":false,"sender":{"key":"jengelh@computergmbh.de","avatar":null},"body":"\nOn Dec 23 2007 06:13, Jeff Garzik wrote:\n> Another year, another update! :)\n>\n> The kernel hacker's guide to git has received some updates:\n>\n> \thttp://linux.yyz.us/git-howto.html\n>\n\nIt says\n\n\"\"\"Don't forget to download tags from time to time.\n\ngit pull only downloads sha1-indexed object data, and the requested\nremote head. This misses updates to the .git/refs/tags/ and\n.git/refs/heads/ directories. For tags, run git fetch --tags $URL.\"\"\"\n\n\nBut when I do git pull on a simple tracking tree (e.g. git-clone\ntorvalds/linux-2.6.git; git pull;) it automatically grabs new tags.\n"},{"id":"64259","messageId":"4778D1CD.4020001@s5r6.in-berlin.de","threadId":"6100","inReplyTo":"Pine.LNX.4.64.0712310349260.2093@fbirervta.pbzchgretzou.qr","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Stefan Richter","fromEmail":"stefanr@s5r6.in-berlin.de","sentAt":"2007-12-31T11:26:05Z","receivedAt":"2007-12-31T11:26:05Z","isPatch":false,"sender":{"key":"stefanr@s5r6.in-berlin.de","avatar":null},"body":"Jan Engelhardt wrote:\n>> \thttp://linux.yyz.us/git-howto.html\n> \n> It says\n> \n> \"\"\"Don't forget to download tags from time to time.\n> \n> git pull only downloads sha1-indexed object data, and the requested\n> remote head. This misses updates to the .git/refs/tags/ and\n> .git/refs/heads/ directories. For tags, run git fetch --tags $URL.\"\"\"\n> \n> But when I do git pull on a simple tracking tree (e.g. git-clone\n> torvalds/linux-2.6.git; git pull;) it automatically grabs new tags.\n\nA while ago the default behavior of git pull was changed to fetch all\ntags which point to objects that can be reached from any of the tracked\nheads.\n\nOld behaviour: Option --tags was needed to fetch tags at all. Current\nbehavior: Option --tags forces to download all tags and the objects\nthey point to. Option --no-tags works like the old default behavior.\n\nReaders of Kernel Hackers' Guide to git will most certainly have a\nrecent enough version of git so that the \"download_tags\" subsection can\nbe removed without replacement.\n-- \nStefan Richter\n-=====-=-=== ==-- =====\nhttp://arcgraph.de/sr/\n"},{"id":"64268","messageId":"7v4pdy7oub.fsf@gitster.siamese.dyndns.org","threadId":"6100","inReplyTo":"4778D1CD.4020001@s5r6.in-berlin.de","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-12-31T17:31:40Z","receivedAt":"2007-12-31T17:31:40Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Stefan Richter writes:\n\n> Jan Engelhardt wrote:\n>>> \thttp://linux.yyz.us/git-howto.html\n>> \n>> It says\n>> \n>> \"\"\"Don't forget to download tags from time to time.\n>> \n>> git pull only downloads sha1-indexed object data, and the requested\n>> remote head. This misses updates to the .git/refs/tags/ and\n>> .git/refs/heads/ directories. For tags, run git fetch --tags $URL.\"\"\"\n>> \n>> But when I do git pull on a simple tracking tree (e.g. git-clone\n>> torvalds/linux-2.6.git; git pull;) it automatically grabs new tags.\n>\n> A while ago the default behavior of git pull was changed to fetch all\n> tags which point to objects that can be reached from any of the tracked\n> heads.\n>\n> Old behaviour: Option --tags was needed to fetch tags at all. Current\n> behavior: Option --tags forces to download all tags and the objects\n> they point to. Option --no-tags works like the old default behavior.\n>\n> Readers of Kernel Hackers' Guide to git will most certainly have a\n> recent enough version of git so that the \"download_tags\" subsection can\n> be removed without replacement.\n\nAll correct.\n\nThat \"A while ago\" is quite a while ago, though. IIRC it was\nadded very early in 2006, which is eons ago in git timescale.\n"},{"id":"81703","messageId":"486849C0.7050703@garzik.org","threadId":"6100","inReplyTo":"Pine.LNX.4.64.0712310349260.2093@fbirervta.pbzchgretzou.qr","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2008-06-30T02:49:36Z","receivedAt":"2008-06-30T02:49:36Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"Jan Engelhardt wrote:\n> On Dec 23 2007 06:13, Jeff Garzik wrote:\n>> Another year, another update! :)\n>>\n>> The kernel hacker's guide to git has received some updates:\n>>\n>> \thttp://linux.yyz.us/git-howto.html\n>>\n> \n> It says\n> \n> \"\"\"Don't forget to download tags from time to time.\n> \n> git pull only downloads sha1-indexed object data, and the requested\n> remote head. This misses updates to the .git/refs/tags/ and\n> .git/refs/heads/ directories. For tags, run git fetch --tags $URL.\"\"\"\n> \n> \n> But when I do git pull on a simple tracking tree (e.g. git-clone\n> torvalds/linux-2.6.git; git pull;) it automatically grabs new tags.\n\n\n\nUnfortunately tags are not copied in all cases. To this day, I still \nhave to 'git fetch --tags', generally when pulling from one local repo \ninto another. It's annoying that tags don't follow objects, when pulled.\n\n\tJeff\n"},{"id":"81704","messageId":"48684A46.7040802@garzik.org","threadId":"6100","inReplyTo":"4778D1CD.4020001@s5r6.in-berlin.de","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2008-06-30T02:51:50Z","receivedAt":"2008-06-30T02:51:50Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"Stefan Richter wrote:\n> Jan Engelhardt wrote:\n>>> \thttp://linux.yyz.us/git-howto.html\n>> It says\n>>\n>> \"\"\"Don't forget to download tags from time to time.\n>>\n>> git pull only downloads sha1-indexed object data, and the requested\n>> remote head. This misses updates to the .git/refs/tags/ and\n>> .git/refs/heads/ directories. For tags, run git fetch --tags $URL.\"\"\"\n>>\n>> But when I do git pull on a simple tracking tree (e.g. git-clone\n>> torvalds/linux-2.6.git; git pull;) it automatically grabs new tags.\n> \n> A while ago the default behavior of git pull was changed to fetch all\n> tags which point to objects that can be reached from any of the tracked\n> heads.\n\n\nThis does not work in all cases. When I retrieve the latest kernel, it \ndownloads the tags:\n\n\tcd /spare/repo/linux-2.6\n\tgit pull\n\nbut when I pull those changes into another local repo, the tags do -not- \nfollow the objects:\n\n\tcd /spare/repo/misc-2.6\n\tgit checkout master\n\tgit pull ../linux-2.6\n\tgit fetch --tags ../linux-2.6\t# still required to this day\n\nRegards,\n\n\tJeff\n"},{"id":"81720","messageId":"48687CDE.5010502@s5r6.in-berlin.de","threadId":"6100","inReplyTo":"48684A46.7040802@garzik.org","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Stefan Richter","fromEmail":"stefanr@s5r6.in-berlin.de","sentAt":"2008-06-30T06:27:42Z","receivedAt":"2008-06-30T06:27:42Z","isPatch":false,"sender":{"key":"stefanr@s5r6.in-berlin.de","avatar":null},"body":"Jeff Garzik wrote:\n> Stefan Richter wrote:\n>> A while ago the default behavior of git pull was changed to fetch all\n>> tags which point to objects that can be reached from any of the tracked\n>> heads.\n> \n> \n> This does not work in all cases. When I retrieve the latest kernel, it \n> downloads the tags:\n> \n> cd /spare/repo/linux-2.6\n> git pull\n> \n> but when I pull those changes into another local repo, the tags do -not- \n> follow the objects:\n> \n> cd /spare/repo/misc-2.6\n> git checkout master\n> git pull ../linux-2.6\n> git fetch --tags ../linux-2.6 # still required to this day\n\nI guess this is because /spare/repo/misc-2.6 does not have branches of \n/spare/repo/linux-2.6 configured as remote (tracking) branches.\n-- \nStefan Richter\n-=====-==--- -==- ====-\nhttp://arcgraph.de/sr/\n"},{"id":"82094","messageId":"200807030827.00086.chriscool@tuxfamily.org","threadId":"6100","inReplyTo":"486849C0.7050703@garzik.org","subject":"Re: Updated Kernel Hacker's guide to git","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2008-07-03T06:26:59Z","receivedAt":"2008-07-03T06:26:59Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi,\n\nLe lundi 30 juin 2008, Jeff Garzik a écrit :\n> Jan Engelhardt wrote:\n> > On Dec 23 2007 06:13, Jeff Garzik wrote:\n> >> Another year, another update! :)\n> >>\n> >> The kernel hacker's guide to git has received some updates:\n> >>\n> >> \thttp://linux.yyz.us/git-howto.html\n\nMay I suggest adding some stuff about \"git bisect\", or at least links to \nother documentation about it, in this guide?\n\nEspecially, you may want to add an example about how to automate testing \nusing \"git bisect run\" as you suggest other to do that:\n\nhttp://www.ussg.iu.edu/hypermail/linux/kernel/0804.1/0633.html\n\nThanks in advance,\nChristian.\n"}]}