similar to: Reminder: Issues and Code Contribution move to GitHub

In order to reduce the amount of system maintenance and administration that needs to be done by the Asterisk team at Sangoma, we've decided to move capabilities such as issue tracking, code management/review and documentation/wiki to hosted solutions. Last year, we compared GitHub and GitLab and while the evaluation of documentation/wiki alternatives is still ongoing, we've decided that

Please join us today at 9AM PDT, 12 Noon EDT for the VoIP Users Conference to talk about the latest news and events in the wonderful world of VoIP. IRC #voip-users-conference SIP 7463#22622#1 at proxy.ideasip.com for g711 SIP 200901 at login.zipdx.com (for g722 wideband-capable devices) See http://VUC.me for more details /r

Hi, We are still on track to retire SVN and complete the transition to GitHub by Oct 21, 2019 (This year's US Dev Meeting). Even though this 3+ months away, it is very important that you begin to migrate your workflows to GitHub as soon as possible. For developers, this means using the git-llvm script to commit changes and for CI systems or other read-only use cases can begin fetching code

I've found that for first-time users (myself included) it's easy to accidentally commit a series of SVN commits with git llvm push. If we expect that a lot of folks will be switching over, might it be worth adding a warning to the script when more than one commit will be pushed? On Fri, Jul 12, 2019 at 12:48 PM James Y Knight via cfe-dev < cfe-dev at lists.llvm.org> wrote: > On

Hi Lei, > On Jun 20, 2015, at 11:21 AM, Lei Yang <yltt1234512 at gmail.com> wrote: I am sorry it has taken me so long to test this workflow. > Hi, > > Kunaal and I have completed a prototype of the first part of our GSoC project (implement a new doc toolchain). Our goal is to implement a doc toolchain for short how-to docs and lower the barrier for new comers to contribute.

On Wed, Feb 24, 2016 at 10:21 PM Pete Cooper via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > Sent from my iPhone > > > On Feb 24, 2016, at 6:25 PM, Chandler Carruth via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > I just want to clarify in case anyone is confused: I am in no way > suggesting that we would use pull requests,

We are looking to implement a code review system that will require a review of the code before it gets to production servers. I have been looking into many different options, and would love some feedback and experiences from other users. Our puppet is in a git repo. We have 3 primary environments with a branch of puppet for each of them. All of our puppet info is in the git repo

On Wed, Jun 1, 2016 at 1:07 PM, Manuel Jacob via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 2016-05-31 22:45, Mehdi Amini via llvm-dev wrote: > >> On May 31, 2016, at 1:31 PM, Renato Golin <renato.golin at linaro.org> >>> wrote: >>> >>> On 31 May 2016 at 21:28, Mehdi Amini <mehdi.amini at apple.com> wrote: >>>

>> As for updating the meta repository: We could disable write access for the normal llvm developer and delegate the submodule bumping to an external >> server. I believe this would be an easy enough job for buildbot or jenkins. > > The plan is to disable all write access to this repository (otherwise > we'll create a nightmare). Having an external counter could be >

On Wed, 15 Jan 2020 at 10:47, Doerfert, Johannes <jdoerfert at anl.gov> wrote: > > I still find Phab to be inscrutable. I don't use any of its advanced > > features. I'm a long-time contributor. > > I asked a similar question in this thread in the very beginning: What > actual problems do you have with Phab? There might be usable solutions > out there

On 31 May 2016 at 21:28, Mehdi Amini <mehdi.amini at apple.com> wrote: > Ideally, I'd prefer the cross-repository to be handled with an extra layer, in a way similar as described in: https://gerrit-review.googlesource.com/Documentation/user-submodules.htm (somehow conceptually similar to Android manifests XML files). > It would be easy to have tooling/scripts for llvm that would

On 27 June 2016 at 01:20, Matthias Braun <matze at braunis.de> wrote: > I really liked the the solution proposed earlier in this thread: Do nothing server side, but instead use > `git rev-list --count master` on the client side (which takes 0.9s on my machine) to get the number of the commit. So nothing to do on the ID part IMO. Mehdi replied to this proposal: "it does not help

Quick reminder before Astricon (from which we will be reporting from live): Tomorrow's guest will be VoIP author Alex Robar. Alex has worked with open source telephony solutions for the past four years, and has collaborated on the development and growth of an international Asterisk-based VoIP peering network. His book is FreePBX 2.5 Powerful Telephony Solutions and we'll be chatting with

On Thu, Jul 9, 2015 at 1:19 AM, Brian (bex) Exelbierd <bex at pobox.com> wrote: > Hi Lei, > > Hi, I am Kunaal the other GSoC student working on this toolchain. > On Jun 20, 2015, at 11:21 AM, Lei Yang <yltt1234512 at gmail.com> wrote: > > > I am sorry it has taken me so long to test this workflow. > Thanks a lot! We need testers and input from community.

Hi, As usual, you can get all the dial in information at http://VoipUsersConference.org IRC is on Freenode.net #voip-users-conference join this even if you can't call in. Call via SIP: talkshoe at vuc.onsip.com (thanks to OnSip.com) Call via PSTN (724) 444-7444 DTMF 22622# 1# or try this: 7463#22622#1 at proxy.ideasip.com (thanks to IdeaSIP.com) or to just look up talkshoe server IP:

Morning! This may be the "day of the dead" in some regions, but we expect the usual lively discussion today at 9AM PDT, 11 Central, 12 Noon EDT, 4PM UK and Portugal, 5PM Paris, $deity-forsaken hour down under. This Sunday, I believe the USA falls back to Standard time. Future VUC are still at 12 Noon EST. Info site: http://voipusersconference.org PSTN (724) 444-7444 enter 22622# 1#

On Thu, Jul 09, 2015 at 02:11:26AM +0530, kunaal jain wrote: > On Thu, Jul 9, 2015 at 1:19 AM, Brian (bex) Exelbierd <bex at pobox.com> > They have both a private git (with gerrit) and a github repo.A If you > open a PR on github it is closed by a bot with instructions to submit > the PR via gerrit to their private repo.A When the PR is resolved and >

Hi Richard, We've added zero and flush functionality to imageio-daemon. You can download and test the latest build (for el7/fc) from: - http://jenkins.ovirt.org/job/ovirt-imageio_master_build-artifacts-el7-x86_64/200/artifact/exported-artifacts/ - http://jenkins.ovirt.org/job/ovirt-imageio_master_build-artifacts-fc27-x86_64/53/artifact/exported-artifacts/ -

On Wed, Feb 24, 2016 at 11:36 PM Joachim Durchholz via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Am 25.02.2016 um 03:25 schrieb Chandler Carruth: > > I just want to clarify in case anyone is confused: I am in no way > > suggesting that we would use pull requests, issues, or anything else as > > part of the workflow for the test suite. I'm fine if folks want to

Already Friday, the week went by in a Flash. If you haven't yet registered for a free Sipgate DID, I suggest you go do so. If you are in, or interested in the business, Sipgate has a few tricks up their sleeves and you should be aware of them. Someone from Sipgate will be joining the conference, which begins at 12 Noon EDT (9AM PDT, 10 Mountain, 11 Central, 5PM UK, 6 Central Europe) ZipDX