[announce] gc

[announce] gc

[Stephen Haberman]

Hi,

This is just a small collections of hooks, scripts, and practices I
developed while working on a not-distributed/corporate project.

A quick list is: svn-like revision numbers (via tagging every commit)
(don't flame me, please), combined diff-enabled commit emails*, Hudson
hooks, trac hooks, branch locking, same-repo-separate-DAG git
server-side config storage and export-on-push, and developer-side
push/pull scripts that "just work".

http://github.com/stephenh/gc

Hopefully others find it as useful.

Thanks,
Stephen

Re: [announce] gc

[Matthieu Moy]

Stephen Haberman <stephen@exigencecorp.com> writes:

> Hi,
>
> This is just a small collections of hooks, scripts, and practices I
> developed while working on a not-distributed/corporate project.

You should find a better name. I mean, one for which

  http://www.google.com/search?q=git+YOUR-NAME-HERE

has a chance to find you ...

My 2 cents,

-- 
Matthieu

Re: [announce] gc

[Stephen Haberman]

> You should find a better name. I mean, one for which
> 
>   http://www.google.com/search?q=git+YOUR-NAME-HERE
> 
> has a chance to find you ...

Ah, good point.

Perhaps "git corporate hooks" or "git enterprise hooks".

I'm a little cautious about using words like corporate/enterprise as
there is nothing exclusively "corporate/enterprise" about any of the
hooks in the project, we just happened to be on a corporate/enterprise
project when we came up with them.

"git enterprise hooks" seems like a potentially good name. I can't see
people googling explicitly for the "enterprise" keyword, but the "git
hooks" seems fairly likely.

Suggestions are welcome and thanks for the feedback.

- Stephen

Re: [announce] gc

[Mike Ralphson]

2008/12/23 Stephen Haberman <stephen@exigencecorp.com>
>
> > You should find a better name. I mean, one for which
> >
> >   http://www.google.com/search?q=git+YOUR-NAME-HERE
> >
> > has a chance to find you ...
>
> Ah, good point.
>
> Perhaps "git corporate hooks" or "git enterprise hooks".
>
> I'm a little cautious about using words like corporate/enterprise as
> there is nothing exclusively "corporate/enterprise" about any of the
> hooks in the project, we just happened to be on a corporate/enterprise
> project when we came up with them.

As the workflows these seem to support are centralised (as you say
these apply equally well in some non-corporate / enterprise projects),
how about git-central?

Mike

Re: [announce] gc

[Stephen Haberman]

> > I'm a little cautious about using words like corporate/enterprise as
> > there is nothing exclusively "corporate/enterprise" about any of the
> > hooks in the project, we just happened to be on a corporate/enterprise
> > project when we came up with them.
> 
> As the workflows these seem to support are centralised (as you say
> these apply equally well in some non-corporate / enterprise projects),
> how about git-central?

Ah, that's excellent. Thanks for the suggestion.

- Stephen

Re: [announce] gc

[Jakub Narebski]

Stephen Haberman wrote:

> This is just a small collections of hooks, scripts, and practices I
> developed while working on a not-distributed/corporate project.
> 
> A quick list is: svn-like revision numbers (via tagging every commit)
> (don't flame me, please), combined diff-enabled commit emails*, Hudson
> hooks, trac hooks, branch locking, same-repo-separate-DAG git
> server-side config storage and export-on-push, and developer-side
> push/pull scripts that "just work".
> 
> http://github.com/stephenh/gc
> 
> Hopefully others find it as useful.

Added to http://git.or.cz/gitwiki/InterfacesFrontendsAndTools
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git