Re: thoughts on a possible "pre-upload" hook
- From
Randal L. Schwartz <merlyn@stonehenge.com>
- Date
- Sep 22, 2009, 16:00 UTC
- Message-ID
- <867hvr2cms.fsf@blue.stonehenge.com>
- In-Reply-To
- <2e24e5b90909220320rbd5fd1l40c7898656445232@mail.gmail.com>
>>>>> "Sitaram" == Sitaram Chamarty <sitaramc@gmail.com> writes:
Sitaram> Hello, Sitaram> As git is used more and more in corporate-type environments, at some Sitaram> point it becomes convenient to have *branches* (or more accurately, Sitaram> refs) that are not readable. The simplest way to do this (from git's Sitaram> point of view) is to allow a "pre-upload" hook, rather like the Sitaram> "pre-receive" hook or "update" hook.
It would seem that you would need to do this even before the commit. So you're looking for the pre-commit hook. Otherwise, the commit is invalid, because it doesn't accurately represent everything it references. And the commit is the unit of transfer between repos.
-- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion