{"thread":{"id":"10846","subject":"Git and Scmbug integration","startedAt":"2007-11-13T19:06:32Z","lastAt":"2008-08-13T09:23:05Z","messageCount":17,"participants":["Kristis Makris","David Symonds","Alex Riesen","Junio C Hamano","Martin Langhoff"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"59692","messageId":"1194980792.4106.6.camel@localhost","threadId":"10846","inReplyTo":null,"subject":"Git and Scmbug integration","fromName":"Kristis Makris","fromEmail":"kristis.makris-ttjs1oqo2yy@public.gmane.org","sentAt":"2007-11-13T19:06:32Z","receivedAt":"2007-11-13T19:06:32Z","isPatch":false,"sender":{"key":"kristis.makris-ttjs1oqo2yy@public.gmane.org","avatar":null},"body":"Hello,\n\nI've been working on adding Git support in Scmbug, a system that\nintegrates software configuration management with bug-tracking. I've run\nacross what seem to be limitations in the Git hooks mechanism (at least\nin version 1.5.1.3). In particular:\n\n\n(1)\n\nhttp://bugzilla.mkgnu.net/show_bug.cgi?id=991\n\nThere's no hook that will trigger when a tag is applied.\n\n\n(2)\n\nhttp://bugzilla.mkgnu.net/show_bug.cgi?id=992\n\nGit does not offer metadata describing a change on the commit trigger\n\nThe commit trigger seems to be \"post-commit\" but it supplies no arguments. The\n\"update\" trigger supplies a lot of information but that's only triggered when\nchanges are published to a remote repository.\n\n\nI could not find a way to extract this information from what I've read in:\n\nhttp://www.kernel.org/pub/software/scm/git/docs/hooks.html\n\n\nAre there plans to implement these hooks ? Or, could someone help me\nunderstand how to extract such information ? \n\n\nThanks,\nKristis\n\n\n_______________________________________________\nscmbug-users mailing list\nscmbug-users-G8y9j4K4DsPiwOUmbS1EgQ@public.gmane.org\nhttp://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users\n"},{"id":"59764","messageId":"ee77f5c20711131500h6ee067ffv3e488ac7bde1d22c@mail.gmail.com","threadId":"10846","inReplyTo":"1194980792.4106.6.camel@localhost","subject":"Re: Git and Scmbug integration","fromName":"David Symonds","fromEmail":"dsymonds@gmail.com","sentAt":"2007-11-13T23:00:49Z","receivedAt":"2007-11-13T23:00:49Z","isPatch":false,"sender":{"key":"dsymonds@gmail.com","avatar":"https://gravatar.com/avatar/b22f5051cbfc11836e36cf7a690e6cde4e225d835e13295ff98d15c7a9ee3c0f?d=mp&s=160"},"body":"On Nov 14, 2007 6:06 AM, Kristis Makris wrote:\n> Hello,\n>\n> I've been working on adding Git support in Scmbug, a system that\n> integrates software configuration management with bug-tracking. I've run\n> across what seem to be limitations in the Git hooks mechanism (at least\n> in version 1.5.1.3). In particular:\n>\n>\n> (1)\n>\n> http://bugzilla.mkgnu.net/show_bug.cgi?id=991\n>\n> There's no hook that will trigger when a tag is applied.\n\nI believe the 'update' hook is run when the tag is pushed.\n\n> (2)\n>\n> http://bugzilla.mkgnu.net/show_bug.cgi?id=992\n>\n> Git does not offer metadata describing a change on the commit trigger\n>\n> The commit trigger seems to be \"post-commit\" but it supplies no arguments. The\n> \"update\" trigger supplies a lot of information but that's only triggered when\n> changes are published to a remote repository.\n\nIsn't this some kind of centralised bug-tracking system anyway? It\nwould be nice, I see, for the 'commit' hook to take, say, the commit\nSHA-1 hash as a parameter.\n\n\nDave.\n"},{"id":"59774","messageId":"20071113234722.GK3268@steel.home","threadId":"10846","inReplyTo":"1194980792.4106.6.camel@localhost","subject":"Re: Git and Scmbug integration","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-11-13T23:47:22Z","receivedAt":"2007-11-13T23:47:22Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Kristis Makris, Tue, Nov 13, 2007 20:06:32 +0100:\n> http://bugzilla.mkgnu.net/show_bug.cgi?id=991\n> \n> There's no hook that will trigger when a tag is applied.\n\nwhat for?\n\n> http://bugzilla.mkgnu.net/show_bug.cgi?id=992\n> \n> Git does not offer metadata describing a change on the commit trigger\n> \n> The commit trigger seems to be \"post-commit\" but it supplies no arguments.\n\nHEAD?\n"},{"id":"59775","messageId":"ee77f5c20711131553j587cb566id6d76bd23182dd6@mail.gmail.com","threadId":"10846","inReplyTo":"20071113234722.GK3268@steel.home","subject":"Re: Git and Scmbug integration","fromName":"David Symonds","fromEmail":"dsymonds@gmail.com","sentAt":"2007-11-13T23:53:43Z","receivedAt":"2007-11-13T23:53:43Z","isPatch":false,"sender":{"key":"dsymonds@gmail.com","avatar":"https://gravatar.com/avatar/b22f5051cbfc11836e36cf7a690e6cde4e225d835e13295ff98d15c7a9ee3c0f?d=mp&s=160"},"body":"On Nov 14, 2007 10:47 AM, Alex Riesen wrote:\n> Kristis Makris, Tue, Nov 13, 2007 20:06:32 +0100:\n> > http://bugzilla.mkgnu.net/show_bug.cgi?id=991\n> >\n> > There's no hook that will trigger when a tag is applied.\n>\n> what for?\n>\n> > http://bugzilla.mkgnu.net/show_bug.cgi?id=992\n> >\n> > Git does not offer metadata describing a change on the commit trigger\n> >\n> > The commit trigger seems to be \"post-commit\" but it supplies no arguments.\n>\n> HEAD?\n\nThat wouldn't be particularly safe if you have a very quick succession\nof commits (say, via a rebase, or automated operations) because HEAD\ncould be moved by the time the post-commit hook reads it.\n\n\nDave.\n"},{"id":"59776","messageId":"1194998142.4106.24.camel@localhost","threadId":"10846","inReplyTo":"ee77f5c20711131500h6ee067ffv3e488ac7bde1d22c@mail.gmail.com","subject":"Re: Git and Scmbug integration","fromName":"Kristis Makris","fromEmail":"kristis.makris@asu.edu","sentAt":"2007-11-13T23:55:42Z","receivedAt":"2007-11-13T23:55:42Z","isPatch":false,"sender":{"key":"kristis.makris@asu.edu","avatar":null},"body":"On Wed, 2007-11-14 at 10:00 +1100, David Symonds wrote:\n> > http://bugzilla.mkgnu.net/show_bug.cgi?id=991\n> >\n> > There's no hook that will trigger when a tag is applied.\n> \n> I believe the 'update' hook is run when the tag is pushed.\n\nEven if that is true, there no hook that will trigger when a local tag\nis applied.\n\n> > (2)\n> >\n> > http://bugzilla.mkgnu.net/show_bug.cgi?id=992\n> >\n> > Git does not offer metadata describing a change on the commit trigger\n> >\n> > The commit trigger seems to be \"post-commit\" but it supplies no arguments. The\n> > \"update\" trigger supplies a lot of information but that's only triggered when\n> > changes are published to a remote repository.\n> \n> Isn't this some kind of centralised bug-tracking system anyway? It\n> would be nice, I see, for the 'commit' hook to take, say, the commit\n> SHA-1 hash as a parameter.\n\nIt isn't a centralized bug-tracking system necessarily. Because\ndifferent developers may used different, custom bug-tracking systems,\nwith custom hooks in their own local Git repositories that integrate\nwith only their own bug-tracking systems. And perhaps we can add the\nsupport in the Scmbug Git frontend to integrate with a centralized\nbug-tracker only on push operations if desired.\n\nBut we can't explore any of these issues, discussed in the thread below\ntoo, unless we can extract what's needed from the hooks.\n\nhttp://thread.gmane.org/gmane.comp.version-control.git/48981/focus=49011\n\n\nI'd like the commit hook to provide enough information to be able to\ntell which files were modified and their respective old/new version (or\nperhaps their old/new SHA-1 hash). If the new SHA-1 hash can be used to\nextract all that, that's ok with me. But right now there's nothing.\n\n\n"},{"id":"59781","messageId":"1194998493.4106.30.camel@localhost","threadId":"10846","inReplyTo":"20071113234722.GK3268@steel.home","subject":"Re: Git and Scmbug integration","fromName":"Kristis Makris","fromEmail":"kristis.makris@asu.edu","sentAt":"2007-11-14T00:01:33Z","receivedAt":"2007-11-14T00:01:33Z","isPatch":false,"sender":{"key":"kristis.makris@asu.edu","avatar":null},"body":"On Wed, 2007-11-14 at 00:47 +0100, Alex Riesen wrote:\n> > There's no hook that will trigger when a tag is applied.\n> \n> what for?\n\nTo implement the synchronous verification checks provided by Scmbug:\n\nhttp://www.mkgnu.net/?q=scmbug\nhttp://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-23-0/manual/html-single/manual.html#VERIFICATION-CHECKS\n\nIn particular:\n\n(1) Convention-based labeling\n\nhttp://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-23-0/manual/html-single/manual.html#VERIFICATION-CHECKS-CONVENTION-BASED-LABELING\n\n(2) The capability to freeze access to certain branches\n\nhttp://bugzilla.mkgnu.net/show_bug.cgi?id=859\n\n(3) Valid product-name verification\n\nhttp://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-23-0/manual/html-single/manual.html#VERIFICATION-CHECKS-VALID-PRODUCT-NAME\n\n\nThere are a lot more checks, as you can see from the manual, that are\nneeded on a commit trigger, rather than just a tag trigger.\n\nA lot of people find the integration provided by Scmbug useful and some\n(Jakub, back me up here) have requested support for Git.\n\n\n"},{"id":"59784","messageId":"ee77f5c20711131602m5b9042fx72689af53e24ddd2@mail.gmail.com","threadId":"10846","inReplyTo":"1194998142.4106.24.camel@localhost","subject":"Re: Git and Scmbug integration","fromName":"David Symonds","fromEmail":"dsymonds@gmail.com","sentAt":"2007-11-14T00:02:04Z","receivedAt":"2007-11-14T00:02:04Z","isPatch":false,"sender":{"key":"dsymonds@gmail.com","avatar":"https://gravatar.com/avatar/b22f5051cbfc11836e36cf7a690e6cde4e225d835e13295ff98d15c7a9ee3c0f?d=mp&s=160"},"body":"On Nov 14, 2007 10:55 AM, Kristis Makris wrote:\n> On Wed, 2007-11-14 at 10:00 +1100, David Symonds wrote:\n> > > http://bugzilla.mkgnu.net/show_bug.cgi?id=991\n> > >\n> > > There's no hook that will trigger when a tag is applied.\n> >\n> > I believe the 'update' hook is run when the tag is pushed.\n>\n> Even if that is true, there no hook that will trigger when a local tag\n> is applied.\n\nUnannotated tags don't make a proper new object, only a ref. If you\nstick to annotated tags, you'll get new objects added which, I think,\nshould trigger the post-commit hook.\n\n> I'd like the commit hook to provide enough information to be able to\n> tell which files were modified and their respective old/new version (or\n> perhaps their old/new SHA-1 hash). If the new SHA-1 hash can be used to\n> extract all that, that's ok with me. But right now there's nothing.\n\nIf you have the new commit's SHA-1, it's very simple to get the parent\ncommit's SHA-1 and do whatever you want. A complexity would be with\nhandling merges, where a commit has multiple parents. If you have a\ncommit SHA-1 hash, you can just \"git diff --name-only ^ \"\nto get a list of the files changed by .\n\n\nDave.\n"},{"id":"59786","messageId":"20071114000457.GM3268@steel.home","threadId":"10846","inReplyTo":"ee77f5c20711131553j587cb566id6d76bd23182dd6@mail.gmail.com","subject":"Re: Git and Scmbug integration","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-11-14T00:04:57Z","receivedAt":"2007-11-14T00:04:57Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"David Symonds, Wed, Nov 14, 2007 00:53:43 +0100:\n> On Nov 14, 2007 10:47 AM, Alex Riesen wrote:\n> > > http://bugzilla.mkgnu.net/show_bug.cgi?id=992\n> > >\n> > > Git does not offer metadata describing a change on the commit trigger\n> > >\n> > > The commit trigger seems to be \"post-commit\" but it supplies no arguments.\n> >\n> > HEAD?\n> \n> That wouldn't be particularly safe if you have a very quick succession\n> of commits (say, via a rebase, or automated operations) because HEAD\n> could be moved by the time the post-commit hook reads it.\n\nHow's that? git-commit waits for its hooks.\n"},{"id":"59788","messageId":"ee77f5c20711131608n6c0b4df4o7eb8a3839a95cdde@mail.gmail.com","threadId":"10846","inReplyTo":"20071114000457.GM3268@steel.home","subject":"Re: Git and Scmbug integration","fromName":"David Symonds","fromEmail":"dsymonds@gmail.com","sentAt":"2007-11-14T00:08:59Z","receivedAt":"2007-11-14T00:08:59Z","isPatch":false,"sender":{"key":"dsymonds@gmail.com","avatar":"https://gravatar.com/avatar/b22f5051cbfc11836e36cf7a690e6cde4e225d835e13295ff98d15c7a9ee3c0f?d=mp&s=160"},"body":"On Nov 14, 2007 11:04 AM, Alex Riesen wrote:\n> David Symonds, Wed, Nov 14, 2007 00:53:43 +0100:\n> > On Nov 14, 2007 10:47 AM, Alex Riesen wrote:\n> > > > http://bugzilla.mkgnu.net/show_bug.cgi?id=992\n> > > >\n> > > > Git does not offer metadata describing a change on the commit trigger\n> > > >\n> > > > The commit trigger seems to be \"post-commit\" but it supplies no arguments.\n> > >\n> > > HEAD?\n> >\n> > That wouldn't be particularly safe if you have a very quick succession\n> > of commits (say, via a rebase, or automated operations) because HEAD\n> > could be moved by the time the post-commit hook reads it.\n>\n> How's that? git-commit waits for its hooks.\n\nOkay, so if it triggers an asynchronous process it just needs to be\ncareful enough to pass whatever HEAD resolves to at the time. Cool.\n\n\nDave.\n"},{"id":"59791","messageId":"1194999404.4106.40.camel@localhost","threadId":"10846","inReplyTo":"ee77f5c20711131602m5b9042fx72689af53e24ddd2@mail.gmail.com","subject":"Re: Git and Scmbug integration","fromName":"Kristis Makris","fromEmail":"kristis.makris@asu.edu","sentAt":"2007-11-14T00:16:44Z","receivedAt":"2007-11-14T00:16:44Z","isPatch":false,"sender":{"key":"kristis.makris@asu.edu","avatar":null},"body":"On Wed, 2007-11-14 at 11:02 +1100, David Symonds wrote:\n> On Nov 14, 2007 10:55 AM, Kristis Makris wrote:\n> > On Wed, 2007-11-14 at 10:00 +1100, David Symonds wrote:\n> > > > http://bugzilla.mkgnu.net/show_bug.cgi?id=991\n> > > >\n> > > > There's no hook that will trigger when a tag is applied.\n> > >\n> > > I believe the 'update' hook is run when the tag is pushed.\n> >\n> > Even if that is true, there no hook that will trigger when a local tag\n> > is applied.\n> \n> Unannotated tags don't make a proper new object, only a ref. If you\n> stick to annotated tags, you'll get new objects added which, I think,\n> should trigger the post-commit hook.\n\nI just tried again tagging with both:\n\n$ git tag TAG_NAME\n\n$ git tag -a TAG_NAME\n\nand I don't get the post-commit hook executed.\n\nPerhaps I missed something ?\n\n> > I'd like the commit hook to provide enough information to be able to\n> > tell which files were modified and their respective old/new version (or\n> > perhaps their old/new SHA-1 hash). If the new SHA-1 hash can be used to\n> > extract all that, that's ok with me. But right now there's nothing.\n> \n> If you have the new commit's SHA-1, it's very simple to get the parent\n> commit's SHA-1 and do whatever you want. A complexity would be with\n> handling merges, where a commit has multiple parents. If you have a\n> commit SHA-1 hash, you can just \"git diff --name-only ^ \"\n> to get a list of the files changed by .\n\nThis sounds great. If the post-commit hook could now provide the new\ncommit SHA-1 hash than that should be what I need.\n\nCan the new commit SHA-1 hash be added as a parameter to the post-commit\nhook please ?\n"},{"id":"59794","messageId":"ee77f5c20711131627q329d45aepe48102728cf2778c@mail.gmail.com","threadId":"10846","inReplyTo":"1194999404.4106.40.camel@localhost","subject":"Re: Git and Scmbug integration","fromName":"David Symonds","fromEmail":"dsymonds@gmail.com","sentAt":"2007-11-14T00:27:40Z","receivedAt":"2007-11-14T00:27:40Z","isPatch":false,"sender":{"key":"dsymonds@gmail.com","avatar":"https://gravatar.com/avatar/b22f5051cbfc11836e36cf7a690e6cde4e225d835e13295ff98d15c7a9ee3c0f?d=mp&s=160"},"body":"On Nov 14, 2007 11:16 AM, Kristis Makris wrote:\n> > Unannotated tags don't make a proper new object, only a ref. If you\n> > stick to annotated tags, you'll get new objects added which, I think,\n> > should trigger the post-commit hook.\n>\n> I just tried again tagging with both:\n>\n> $ git tag TAG_NAME\n>\n> $ git tag -a TAG_NAME\n>\n> and I don't get the post-commit hook executed.\n>\n> Perhaps I missed something ?\n\nOkay, I don't know about that. Someone else might want to weigh in on this.\n\n> > If you have the new commit's SHA-1, it's very simple to get the parent\n> > commit's SHA-1 and do whatever you want. A complexity would be with\n> > handling merges, where a commit has multiple parents. If you have a\n> > commit SHA-1 hash, you can just \"git diff --name-only ^ \"\n> > to get a list of the files changed by .\n>\n> This sounds great. If the post-commit hook could now provide the new\n> commit SHA-1 hash than that should be what I need.\n>\n> Can the new commit SHA-1 hash be added as a parameter to the post-commit\n> hook please ?\n\nSure -- I've got a patch for it that I'll send shortly. It's using the\nexisting shell git-commit, so might be suitable for maint; I haven't\nfollowed what's happened with the builtinification of git-commit.\n\n\nDave.\n"},{"id":"59799","messageId":"7vtznppr8m.fsf@gitster.siamese.dyndns.org","threadId":"10846","inReplyTo":"1194999404.4106.40.camel@localhost","subject":"Re: Git and Scmbug integration","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-11-14T01:09:45Z","receivedAt":"2007-11-14T01:09:45Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Kristis Makris writes:\n\n> I just tried again tagging with both:\n>\n> $ git tag TAG_NAME\n>\n> $ git tag -a TAG_NAME\n>\n> and I don't get the post-commit hook executed.\n>\n> Perhaps I missed something ?\n\nYou didn't. You did not create any commit. No post-commit hook\nruns. There is no post-tag hook.\n\n> Can the new commit SHA-1 hash be added as a parameter to the post-commit\n> hook please ?\n\nLooking at \"git-rev-parse HEAD\" in your hook should be enough.\n"},{"id":"59800","messageId":"7vprydpr5o.fsf@gitster.siamese.dyndns.org","threadId":"10846","inReplyTo":"ee77f5c20711131627q329d45aepe48102728cf2778c@mail.gmail.com","subject":"Re: Git and Scmbug integration","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-11-14T01:11:31Z","receivedAt":"2007-11-14T01:11:31Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"David Symonds\" writes:\n\n> Sure -- I've got a patch for it that I'll send shortly. It's using the\n> existing shell git-commit, so might be suitable for maint; I haven't\n> followed what's happened with the builtinification of git-commit.\n\nNo, 'maint' won't get a feature enhancements.\n\nAgain, why isn't reading HEAD enough?\n"},{"id":"59802","messageId":"ee77f5c20711131716l6dd1dccjcb3ff5f3a54c9359@mail.gmail.com","threadId":"10846","inReplyTo":"7vprydpr5o.fsf@gitster.siamese.dyndns.org","subject":"Re: Git and Scmbug integration","fromName":"David Symonds","fromEmail":"dsymonds@gmail.com","sentAt":"2007-11-14T01:16:47Z","receivedAt":"2007-11-14T01:16:47Z","isPatch":false,"sender":{"key":"dsymonds@gmail.com","avatar":"https://gravatar.com/avatar/b22f5051cbfc11836e36cf7a690e6cde4e225d835e13295ff98d15c7a9ee3c0f?d=mp&s=160"},"body":"On Nov 14, 2007 12:11 PM, Junio C Hamano wrote:\n> \"David Symonds\" writes:\n>\n> > Sure -- I've got a patch for it that I'll send shortly. It's using the\n> > existing shell git-commit, so might be suitable for maint; I haven't\n> > followed what's happened with the builtinification of git-commit.\n>\n> No, 'maint' won't get a feature enhancements.\n\nFair enough.\n\n> Again, why isn't reading HEAD enough?\n\nReading HEAD would be fine. I guess it just seems a sensible and more\ndirect path to passing that information so that the hook has less to\ndo. It seems quite a simple thing that would be very helpful to hook\nwriters, with zero impact on everyone else.\n\n\nDave.\n"},{"id":"59803","messageId":"7vk5olpqep.fsf@gitster.siamese.dyndns.org","threadId":"10846","inReplyTo":"ee77f5c20711131716l6dd1dccjcb3ff5f3a54c9359@mail.gmail.com","subject":"Re: Git and Scmbug integration","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-11-14T01:27:42Z","receivedAt":"2007-11-14T01:27:42Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"David Symonds\" writes:\n\n> Reading HEAD would be fine. I guess it just seems a sensible and more\n> direct path to passing that information so that the hook has less to\n> do. It seems quite a simple thing that would be very helpful to hook\n> writers, with zero impact on everyone else.\n\nYou cannot just say \"The hook did not get any parameter, nobody\nwould have cared, this does not regress.\"\n\nSome anal people could have checked and checked \"test $# = 0\" at\nthe beginning to make sure their hooks do not get broken by\nrandom interface changes on the git side. Now their carefully\nwritten script errors out as designed. Also some people seem to\nuse different version of git on the same repository (e.g. NFS\nmounted across hosts that run different versions of git).\n\nI would 80% agree with you if the post-comit hook interface were\nwritten in the way your patch does from day one. Unfortunately\nthat is not the case.\n\nThe remaining 20%? If we _were_ to change the hook interface, I\nwould also pass which branch the commit is added to, in addition\nto what commit it is.\n\nBoth are easily obtainable by reading HEAD (you need to read\nHEAD twice, though) but would be handy.\n"},{"id":"59816","messageId":"46a038f90711132208r4daf477cle54f2feb95852cdb@mail.gmail.com","threadId":"10846","inReplyTo":"1194998142.4106.24.camel@localhost","subject":"Re: Git and Scmbug integration","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2007-11-14T06:08:04Z","receivedAt":"2007-11-14T06:08:04Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On Nov 14, 2007 12:55 PM, Kristis Makris wrote:\n> It isn't a centralized bug-tracking system necessarily. Because\n> different developers may used different, custom bug-tracking systems,\n> with custom hooks in their own local Git repositories that integrate\n> with only their own bug-tracking systems. And perhaps we can add the\n> support in the Scmbug Git frontend to integrate with a centralized\n> bug-tracker only on push operations if desired.\n\nI disagree somewhat here. In git, local commits are extremely\nlightweight, and as a developer I don't want anything remarkable to\nhappen on those, even locally. It's pushing (which is actually\npublishing!) that makes those commits relevant.\n\nEven if I have a local or distributed bugtracker, any purely local\ncommit is \"draft\".\n\nAnd this is regardless of centralised or distributed -- that's a\nmatter of policy around the repo I'm pushing to. The distinction that\nmatters is local vs published. Local commits get removed, rebased,\nredone, discarded a whole lot.\n\n> But we can't explore any of these issues, discussed in the thread below\n> too, unless we can extract what's needed from the hooks.\n\nI concur with the chorus that chants \"HEAD\"... try with `git show\nHEAD` for starters...\n\ncheers,\n\n\nmartin\n"},{"id":"87450","messageId":"1218619385.4058.0.camel@localhost","threadId":"10846","inReplyTo":"7vtznppr8m.fsf-jO8aZxhGsIagbBziECNbOZn29agUkmeCHZ5vskTnxNA@public.gmane.org","subject":"Re: Git and Scmbug integration","fromName":"Kristis Makris","fromEmail":"kristis.makris-ttjs1oqo2yy@public.gmane.org","sentAt":"2008-08-13T09:23:05Z","receivedAt":"2008-08-13T09:23:05Z","isPatch":false,"sender":{"key":"kristis.makris-ttjs1oqo2yy@public.gmane.org","avatar":null},"body":"On Tue, 2007-11-13 at 17:09 -0800, Junio C Hamano wrote:\n> Kristis Makris writes:\n> \n> > I just tried again tagging with both:\n> >\n> > $ git tag TAG_NAME\n> >\n> > $ git tag -a TAG_NAME\n> >\n> > and I don't get the post-commit hook executed.\n> >\n> > Perhaps I missed something ?\n> \n> You didn't. You did not create any commit. No post-commit hook\n> runs. There is no post-tag hook.\n> \n> > Can the new commit SHA-1 hash be added as a parameter to the post-commit\n> > hook please ?\n> \n> Looking at \"git-rev-parse HEAD\" in your hook should be enough.\n\nBut ... which hook ? There is not post-tag hook!! \n\n\n_______________________________________________\nscmbug-users mailing list\nscmbug-users-G8y9j4K4DsPiwOUmbS1EgQ@public.gmane.org\nhttp://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users\n"}]}