<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/templates/hooks--update.sample, branch v1.6.3</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v1.6.3</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v1.6.3'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2009-04-18T04:26:11Z</updated>
<entry>
<title>hook/update: example of how to prevent branch creation</title>
<updated>2009-04-18T04:26:11Z</updated>
<author>
<name>Pierre Habouzit</name>
<email>madcoder@debian.org</email>
</author>
<published>2009-04-16T20:00:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=aed97c677cdfd1b9bbc9b33b5418ad4a29109082'/>
<id>urn:sha1:aed97c677cdfd1b9bbc9b33b5418ad4a29109082</id>
<content type='text'>
Since git doesn't provide a receive.denyBranchCreation or similar, here is
an example of how to be sure users cannot create branches remotely by
pushing a new reference.

This setup has been proven useful to prevent creation of spurious branches
because of users having their remote.origin.push set to HEAD, when they
use `git push` while being on a local topic branch of theirs instead of
the proper one.

Signed-off-by: Pierre Habouzit &lt;madcoder@debian.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Modify description file to say what this file is</title>
<updated>2009-03-04T08:56:52Z</updated>
<author>
<name>John Tapsell</name>
<email>johnflux@gmail.com</email>
</author>
<published>2009-02-19T07:36:00Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=28001d0873cfce1ad6a44f1c2deaf9388d953cc3'/>
<id>urn:sha1:28001d0873cfce1ad6a44f1c2deaf9388d953cc3</id>
<content type='text'>
A lot of people see this message for the first time on the gitweb
interface, where there is no clue as to what 'this file' means.

Signed-off-by: John Tapsell &lt;johnflux@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Ship sample hooks with .sample suffix</title>
<updated>2008-06-25T02:06:22Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-06-25T01:45:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=f98f8cbac01e0d5dbb30660d7ea70af6a1439dfd'/>
<id>urn:sha1:f98f8cbac01e0d5dbb30660d7ea70af6a1439dfd</id>
<content type='text'>
We used to mark hooks we ship as samples by making them unexecutable, but
some filesystems cannot tell what is executable and what is not.

This makes it much more explicit.  The hooks are suffixed with .sample
(but now are made executable), so enabling it is still one step operation
(instead of "chmod +x $hook", you would do "mv $hook.sample $hook") but
now they won't get accidentally enabled on systems without executable bit.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
