{"thread":{"id":"16841","subject":"[announce] gc","startedAt":"2008-12-23T03:24:07Z","lastAt":"2009-01-14T01:31:18Z","messageCount":6,"participants":["Stephen Haberman","Matthieu Moy","Mike Ralphson","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"98588","messageId":"20081222212407.47c9ab1e.stephen@exigencecorp.com","threadId":"16841","inReplyTo":null,"subject":"[announce] gc","fromName":"Stephen Haberman","fromEmail":"stephen@exigencecorp.com","sentAt":"2008-12-23T03:24:07Z","receivedAt":"2008-12-23T03:24:07Z","isPatch":false,"sender":{"key":"stephen@exigencecorp.com","avatar":"https://gravatar.com/avatar/23b93ad70a06ce53505f17ddba65176edbcfb6588e7a4c1a2dca04aaf0a6aff1?d=mp&s=160"},"body":"Hi,\n\nThis is just a small collections of hooks, scripts, and practices I\ndeveloped while working on a not-distributed/corporate project.\n\nA quick list is: svn-like revision numbers (via tagging every commit)\n(don't flame me, please), combined diff-enabled commit emails*, Hudson\nhooks, trac hooks, branch locking, same-repo-separate-DAG git\nserver-side config storage and export-on-push, and developer-side\npush/pull scripts that \"just work\".\n\nhttp://github.com/stephenh/gc\n\nHopefully others find it as useful.\n\nThanks,\nStephen\n"},{"id":"98606","messageId":"vpqabanc9v6.fsf@bauges.imag.fr","threadId":"16841","inReplyTo":"20081222212407.47c9ab1e.stephen@exigencecorp.com","subject":"Re: [announce] gc","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2008-12-23T13:13:49Z","receivedAt":"2008-12-23T13:13:49Z","isPatch":false,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Stephen Haberman writes:\n\n> Hi,\n>\n> This is just a small collections of hooks, scripts, and practices I\n> developed while working on a not-distributed/corporate project.\n\nYou should find a better name. I mean, one for which\n\n http://www.google.com/search?q=git+YOUR-NAME-HERE\n\nhas a chance to find you ...\n\nMy 2 cents,\n\n-- \nMatthieu\n"},{"id":"98609","messageId":"20081223082207.f31ab2a3.stephen@exigencecorp.com","threadId":"16841","inReplyTo":"vpqabanc9v6.fsf@bauges.imag.fr","subject":"Re: [announce] gc","fromName":"Stephen Haberman","fromEmail":"stephen@exigencecorp.com","sentAt":"2008-12-23T14:22:07Z","receivedAt":"2008-12-23T14:22:07Z","isPatch":false,"sender":{"key":"stephen@exigencecorp.com","avatar":"https://gravatar.com/avatar/23b93ad70a06ce53505f17ddba65176edbcfb6588e7a4c1a2dca04aaf0a6aff1?d=mp&s=160"},"body":"\n> You should find a better name. I mean, one for which\n> \n> http://www.google.com/search?q=git+YOUR-NAME-HERE\n> \n> has a chance to find you ...\n\nAh, good point.\n\nPerhaps \"git corporate hooks\" or \"git enterprise hooks\".\n\nI'm a little cautious about using words like corporate/enterprise as\nthere is nothing exclusively \"corporate/enterprise\" about any of the\nhooks in the project, we just happened to be on a corporate/enterprise\nproject when we came up with them.\n\n\"git enterprise hooks\" seems like a potentially good name. I can't see\npeople googling explicitly for the \"enterprise\" keyword, but the \"git\nhooks\" seems fairly likely.\n\nSuggestions are welcome and thanks for the feedback.\n\n- Stephen\n"},{"id":"98616","messageId":"e2b179460812230706p12e4f052v960f162e08011ae6@mail.gmail.com","threadId":"16841","inReplyTo":"20081223082207.f31ab2a3.stephen@exigencecorp.com","subject":"Re: [announce] gc","fromName":"Mike Ralphson","fromEmail":"mike.ralphson@gmail.com","sentAt":"2008-12-23T15:06:24Z","receivedAt":"2008-12-23T15:06:24Z","isPatch":false,"sender":{"key":"mike.ralphson@gmail.com","avatar":"https://avatars.githubusercontent.com/u/21603?v=4"},"body":"2008/12/23 Stephen Haberman \n>\n> > You should find a better name. I mean, one for which\n> >\n> > http://www.google.com/search?q=git+YOUR-NAME-HERE\n> >\n> > has a chance to find you ...\n>\n> Ah, good point.\n>\n> Perhaps \"git corporate hooks\" or \"git enterprise hooks\".\n>\n> I'm a little cautious about using words like corporate/enterprise as\n> there is nothing exclusively \"corporate/enterprise\" about any of the\n> hooks in the project, we just happened to be on a corporate/enterprise\n> project when we came up with them.\n\nAs the workflows these seem to support are centralised (as you say\nthese apply equally well in some non-corporate / enterprise projects),\nhow about git-central?\n\nMike\n"},{"id":"98693","messageId":"20081225092322.da6930c2.stephen@exigencecorp.com","threadId":"16841","inReplyTo":"e2b179460812230706p12e4f052v960f162e08011ae6@mail.gmail.com","subject":"Re: [announce] gc","fromName":"Stephen Haberman","fromEmail":"stephen@exigencecorp.com","sentAt":"2008-12-25T15:23:22Z","receivedAt":"2008-12-25T15:23:22Z","isPatch":false,"sender":{"key":"stephen@exigencecorp.com","avatar":"https://gravatar.com/avatar/23b93ad70a06ce53505f17ddba65176edbcfb6588e7a4c1a2dca04aaf0a6aff1?d=mp&s=160"},"body":"\n> > I'm a little cautious about using words like corporate/enterprise as\n> > there is nothing exclusively \"corporate/enterprise\" about any of the\n> > hooks in the project, we just happened to be on a corporate/enterprise\n> > project when we came up with them.\n> \n> As the workflows these seem to support are centralised (as you say\n> these apply equally well in some non-corporate / enterprise projects),\n> how about git-central?\n\nAh, that's excellent. Thanks for the suggestion.\n\n- Stephen\n"},{"id":"100349","messageId":"gkjf93$r5e$1@ger.gmane.org","threadId":"16841","inReplyTo":"20081222212407.47c9ab1e.stephen@exigencecorp.com","subject":"Re: [announce] gc","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2009-01-14T01:31:18Z","receivedAt":"2009-01-14T01:31:18Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Stephen Haberman wrote:\n\n> This is just a small collections of hooks, scripts, and practices I\n> developed while working on a not-distributed/corporate project.\n> \n> A quick list is: svn-like revision numbers (via tagging every commit)\n> (don't flame me, please), combined diff-enabled commit emails*, Hudson\n> hooks, trac hooks, branch locking, same-repo-separate-DAG git\n> server-side config storage and export-on-push, and developer-side\n> push/pull scripts that \"just work\".\n> \n> http://github.com/stephenh/gc\n> \n> Hopefully others find it as useful.\n\nAdded to http://git.or.cz/gitwiki/InterfacesFrontendsAndTools\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"}]}