search for: branch_name

Hi All, I read rumors of a potential Asterisk 1.4.12 release for last week. I would like to start testing Asterisk 1.4 on Solaris, but, the fix for the segfault in res_features is only in the current development trunk. I would much rather test a release version, and as such, need to wait for the release of 1.4.12, my question is, do we have a guestimate on when it will be released, 1 week, 2

Hi, we are currently managing our puppet modules with one SVN workspace for each admin. The post commit hook script updates /etc/puppet/ directory and triggers the puppet kick of the correct server. The problem we have with this solution is that sometimes there are many small checkins to one change, because the admin forgot to change small details in the config file, e.g. forgot to change

On Wed, Jun 17, 2015 at 05:57:39AM +0300, Ady via Syslinux wrote: > > After taking over repo.or.cz/syslinux.git, the aforementioned > previously-valid links are no longer valid :(. Perhaps not only "tags" > are no longer valid. > > Also, the "tag" hyperlinks that were visible before are now no longer > there in repo.or.cz/syslinux.git. > > Note

...t;syslinux-6.03" is not shown in the web interface, whereas the "green" /refs/heads/ "master" is seen. Since the "tag" hyperlinks are not currently shown (they were there a couple of days ago), and the "refs" page is currently showing "heads/<branch_name>" but not even one of the "tags/<tag_name>, then I am guessing that the "refs/tags" data needs some additional (manual?) treatment. I am only reporting just in case this cannot be corrected later; if it can, I can wait (hopefully not years :)). Regarding the use of...

...is not shown in > the web interface, whereas the "green" /refs/heads/ "master" is seen. > > Since the "tag" hyperlinks are not currently shown (they were there a > couple of days ago), and the "refs" page is currently showing > "heads/<branch_name>" but not even one of the "tags/<tag_name>, then I > am guessing that the "refs/tags" data needs some additional (manual?) > treatment. It's a brand new repo at the old URL. > I am only reporting just in case this cannot be corrected later; if it > can...

...++++++++++++++++++++++++++++++++++++++++ 1 files changed, 59 insertions(+), 0 deletions(-) diff --git a/git-hook/update b/git-hook/update index ed76bd2..f98a403 100755 --- a/git-hook/update +++ b/git-hook/update @@ -41,6 +41,45 @@ # When this boolean is true, you may not push a merge commit to BRANCH_NAME. # By default, you may. # +# --------------------------------------------------------------------- +# Allow people to change server-side git config in very specific ways. +# To enable this, on the server, you must do something like the following, +# +# git config hooks.server.config-changing.va...