Commit graph

7 commits

Author SHA1 Message Date
Sitaram Chamarty 3ddc9087d3 first production use: @all, leading slash
I had to make two minor fixes while migrating my work repos:

1.  I forgot to honor '@all'; oops!

    While I was about it, I also fixed the "access denied"
    message to show what rights were being tried when it
    failed.

2.  I forgot that URLs can have leading slashes (I myself
    only use URLs like gs:reponame.git, where gs is an ssh
    stanza that describes the git server in question).
2009-08-27 13:26:18 +05:30
Sitaram Chamarty 0a32d46f59 use-warnings 2009-08-26 10:33:00 +05:30
Sitaram Chamarty 09aeb31198 project renamed to gitolite 2009-08-26 06:54:43 +05:30
Sitaram Chamarty 66bf4a20f9 all: lexical file handles instead of bare 2009-08-25 11:06:03 +05:30
Sitaram Chamarty 92cf77d9c2 update hook: squelch message for branch deletion
Ilari pointed out that in case of branch deletion the *new* SHA could be 0,
which causes an ugly

    fatal: Not a valid commit name 0000000000000000000000000000000000000000

Since we consider deletion an extreme form of rewind, the end result does not
change ($merge_base will be unequal to $oldsha anyway), but we do need to
squelch the ugly message.
2009-08-25 06:38:05 +05:30
Sitaram Chamarty 3cddc4ca35 compile/update-hook: preserve the order of refs
...by turning the last piece (list of allowed refs) into an array rather than a hash
2009-08-24 15:06:39 +05:30
Sitaram Chamarty 2e38867b59 add hook, the last piece 2009-08-24 15:06:36 +05:30