From: Dun Peal <dunpealer@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Efficiently detecting paths that differ from each other only in case
Date: Sat, 9 Oct 2010 17:00:10 -0500 [thread overview]
Message-ID: <AANLkTinzH3EWy=E2H9hQJzCdPB3Epu5WQkmuv2CWKFtc@mail.gmail.com> (raw)
In-Reply-To: <m3aamng3dt.fsf@localhost.localdomain>
On Sat, Oct 9, 2010 at 3:47 AM, Jakub Narebski <jnareb@gmail.com> wrote:
> Sidenote: why not detect violation earlier, by having pre-commit hook
> in each developer repository check for such violation? It is not as
> time sensitive on the local side (when creating a commit, you have to
> take some time to write commit message anyway).
That's a solution, but as you surely know hooks are not automatically
cloned with the repository. There's no way to ensure that all of our
many users install that hook, and we can't allow an incorrect state on
the central node.
A pre-receive hook on that node seems like the only way to really ensure that.
D
next prev parent reply other threads:[~2010-10-09 22:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 6:13 Efficiently detecting paths that differ from each other only in case Dun Peal
2010-10-08 13:50 ` Jeff King
2010-10-08 19:44 ` Dun Peal
2010-10-08 19:51 ` Jeff King
2010-10-08 19:57 ` Dun Peal
2010-10-08 20:06 ` Jeff King
2010-10-08 22:57 ` Dun Peal
2010-10-09 8:47 ` Jakub Narebski
2010-10-09 22:00 ` Dun Peal [this message]
2010-10-09 22:31 ` Jakub Narebski
2010-10-11 3:07 ` Jeff King
2010-10-16 22:37 ` Dun Peal
2010-10-17 4:25 ` Jeff King
2010-10-08 19:56 ` Jonathan Nieder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTinzH3EWy=E2H9hQJzCdPB3Epu5WQkmuv2CWKFtc@mail.gmail.com' \
--to=dunpealer@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).