On Wed, Aug 29, 2007 at 04:06:17PM CEST, Johannes Schindelin wrote:
> I think that they are way more than just technical issues: the
> chicken-and-egg problem is certainly _not_ a technical issue.
What do you mean by the chicken-and-egg problem? I think I missed that.
> Besides, another very valid issue is that of portability. Hooks can be
> _any_ executables. Not just scripts. Not just _bash_ scripts.
So? That's really up to whoever maintains the repository to sort out.
> The other issue I raised, however, seemed to die away in the other noise:
>
> _Why_ on earth do you want to put something into the SCM specific
> meta-data which should be part of the build process _to begin with_?
>
> _All_ of the arguments I read are along the lines "we want to enforce some
> coding styles" or similar. These issues are _orthogonal_ to the question
> which SCM is used.
Your company has certain rules on how all the source on the public
branches should look like, etc. It's not quite clear to me how can build
system enforce these rules.
--
Petr "Pasky" Baudis
Early to rise and early to bed makes a male healthy and wealthy and dead.
-- James Thurber
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
