On Wed 2004-12-22 at 16:09:23 -0500, Gili wrote:
> On Wed, 22 Dec 2004 22:02:46 +0100, email@example.com wrote:
> >> and warn the user when necessary at commit time or
> >>checkout time.
> >You can do this toay with a pre-commit hook.
> I'm fine with doing it your way but can you please augment the
> official documentation to show how this can be done? I think this is a
> big enough issue for win32 that it belongs in the book.
The docs already explain pre-commit hooks, what they are good for, and
how to get hooks working in general. And you don't have to write that
pre-commit hook yourself, because their is already one in the contrib
dir, ready to use:
But I agree with you, the FAQ point regarding Windows case issues
could point to that script.
> >Like I said, you can't have a case-insensitive comparison that will work
> >everywhere, because it's locale-dependent. At the very least, that means
> >you can't do the comparison on the server.
> Well, that throws the idea of "pre-commit hooks" out the window
Yes and no. Yes, the problem is, that there is no _general_ solution
to do this on the server, regardless of whether you use hook-scripts
And "no", because the paragraph about hook scripts was not about a
general solution, but simply about the fact that whatever solution you
choose, you don't need server support to warn your users, but can do
that within the pre-commit hook already. It's exists exactly for that
kind of use.
So if you can restrict your clients to a common locale (you'll notice
that kind of discussion at the top of the script mentioned above), you
can setup warnings on your server for this. No extra features
Of course that touches only a small part of the overall issue, but I
only intended to clarify the point about the pre-commit hook.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Dec 23 07:54:53 2004