{"thread":{"id":"5072","subject":"path-restricted gitk with tags showing up?","startedAt":"2006-08-01T17:42:10Z","lastAt":"2006-08-01T19:33:37Z","messageCount":4,"participants":["Olivier Galibert","Linus Torvalds","Sergey Vlasov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"24520","messageId":"20060801174210.GA81699@dspnet.fr.eu.org","threadId":"5072","inReplyTo":null,"subject":"path-restricted gitk with tags showing up?","fromName":"Olivier Galibert","fromEmail":"galibert@pobox.com","sentAt":"2006-08-01T17:42:10Z","receivedAt":"2006-08-01T17:42:10Z","isPatch":false,"sender":{"key":"galibert@pobox.com","avatar":null},"body":"I'd like to do a (f.i) gitk include/sound/asound.h but still see the\ncommits which are in the DAG delimited by the alsa commits and have\ntags attached.  The aim is to know what changes where in what released\nkernel version.  Is there a way to do that?\n\n  OG.\n"},{"id":"24521","messageId":"Pine.LNX.4.64.0608011137580.4168@g5.osdl.org","threadId":"5072","inReplyTo":"20060801174210.GA81699@dspnet.fr.eu.org","subject":"Re: path-restricted gitk with tags showing up?","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2006-08-01T18:39:16Z","receivedAt":"2006-08-01T18:39:16Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Tue, 1 Aug 2006, Olivier Galibert wrote:\n>\n> I'd like to do a (f.i) gitk include/sound/asound.h but still see the\n> commits which are in the DAG delimited by the alsa commits and have\n> tags attached.  The aim is to know what changes where in what released\n> kernel version.  Is there a way to do that?\n\nNot right now. It should be fairly easy to add a flag that marks all \ntagged commits (or, indeed, anything that is reachable from .git/refs/) as \n\"TREECHANGE\" so that they aren't optimized away, but we don't have \nanything like that right now at least.\n\nA small exercise for somebody who wants to get into git, perhaps? Hint, \nhint..\n\n\t\tLinus\n"},{"id":"24522","messageId":"20060801231329.82d934a2.vsu@altlinux.ru","threadId":"5072","inReplyTo":"20060801174210.GA81699@dspnet.fr.eu.org","subject":"Re: path-restricted gitk with tags showing up?","fromName":"Sergey Vlasov","fromEmail":"vsu@altlinux.ru","sentAt":"2006-08-01T19:13:29Z","receivedAt":"2006-08-01T19:13:29Z","isPatch":false,"sender":{"key":"vsu@altlinux.ru","avatar":"https://avatars.githubusercontent.com/u/616082?v=4"},"body":"On Tue, 1 Aug 2006 19:42:10 +0200 Olivier Galibert wrote:\n\n> I'd like to do a (f.i) gitk include/sound/asound.h but still see the\n> commits which are in the DAG delimited by the alsa commits and have\n> tags attached.  The aim is to know what changes where in what released\n> kernel version.  Is there a way to do that?\n\nSince git-1.4.0 gitk shows this information in the \"Follows:\" and\n\"Precedes:\" lines for each commit (you need to enable \"Display nearby\ntags\" in preferences).  In your case, the \"Precedes\" line will show the\nfirst kernel version which included the change.\n\nNote that loading this information takes some time; gitk tries to load\nit in background, so you may see empty \"Follows\" and \"Precedes\" lines\nfor some time.\n"},{"id":"24523","messageId":"20060801193337.GA93307@dspnet.fr.eu.org","threadId":"5072","inReplyTo":"20060801231329.82d934a2.vsu@altlinux.ru","subject":"Re: path-restricted gitk with tags showing up?","fromName":"Olivier Galibert","fromEmail":"galibert@pobox.com","sentAt":"2006-08-01T19:33:37Z","receivedAt":"2006-08-01T19:33:37Z","isPatch":false,"sender":{"key":"galibert@pobox.com","avatar":null},"body":"On Tue, Aug 01, 2006 at 11:13:29PM +0400, Sergey Vlasov wrote:\n> On Tue, 1 Aug 2006 19:42:10 +0200 Olivier Galibert wrote:\n> \n> > I'd like to do a (f.i) gitk include/sound/asound.h but still see the\n> > commits which are in the DAG delimited by the alsa commits and have\n> > tags attached.  The aim is to know what changes where in what released\n> > kernel version.  Is there a way to do that?\n> \n> Since git-1.4.0 gitk shows this information in the \"Follows:\" and\n> \"Precedes:\" lines for each commit (you need to enable \"Display nearby\n> tags\" in preferences).  In your case, the \"Precedes\" line will show the\n> first kernel version which included the change.\n> \n> Note that loading this information takes some time; gitk tries to load\n> it in background, so you may see empty \"Follows\" and \"Precedes\" lines\n> for some time.\n\nWorks rather well, thanks.\n\n  OG.\n"}]}