similar to: Asterisk is moving to Git

Displaying 20 results from an estimated 20000 matches similar to: "Asterisk is moving to Git"

2007 Jun 11
3
RE: Moving to Git
Since you asked for comments... Personally, I'm disappointed to see Speex moving to Git from Subversion. I had just recently learned how easy it is to track progress of Speex using TortoiseSvn. That being said, I'm sure Jean-Marc knows best what the issues may be. How many people are expected to commit on this project this year? -mjc
2007 Jun 11
1
RE: Moving to Git
Svn Log is my favorite! (Butm generally with the Tortoise front-end FWIW. I don't think I've changed anything except back when we needed the AEC patch or to make a project file build. -----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Monday, June 11, 2007 4:27 PM To: Coffey, Michael Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] RE: Moving
2015 Jul 10
0
Finished a prototype of GSoC project: Implement a new doc toolchain
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 >
2016 Jun 30
0
Sequential ID Git hook
I don't think we should do any of that. It's too complicated -- and I don't see the reason to even do it. There's a need for the "llvm-project" repository -- that's been discussed plenty -- but where does the need for a separate "id" that must be pushed into all of the sub-projects come from? This is the first I've heard of that as a thing that needs to
2019 Aug 22
2
h265 codec pass through on asterisk
Well, that sounds pretty straight forward. I can do this and push it to gerrit. Do I need to create a ticket for this? With best regards Florian Floimair Innovation - Software-Development COMMEND INTERNATIONAL GMBH A-5020 Salzburg, Saalachstraße 51 http://www.commend.com <http://www.commend.com/> Security and Communication by Commend FN 178618z | LG Salzburg Am 22.08.19, 11:55
2011 Sep 09
0
[LLVMdev] git Status Update?
On Thu, Sep 8, 2011 at 5:09 PM, David A. Greene <dag at cray.com> wrote: > Bill Wendling <wendling at apple.com> writes: > > >> Let's face it, Joe Dragon is pretty much happy with svn and there's an > >> svn-git bridge for the rest of us. > > The svn-git bridge is broken as several people stated before. It is > easier to contribute code via
2014 Nov 28
2
Switched to git
We've finally completed the move away from subversion, and the master code repository for Xapian is now git. We've had an automatically updated git mirror for more than 4.5 years, so for most people this probably makes little practical difference. The main thing you may notice is that patches and pull requests will now get merged via git, so history can be easily preserved where that
2018 Mar 28
1
Re: Change in ovirt-imageio[master]: Document the random I/O APIs
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/ -
2013 Feb 15
1
Why no line? (ex. from Andy Filed book)
The following script is written by the author of a book on R--Andy Field: You can also download the small datafile, hiccups.dat, from this address: http://www.sagepub.com/dsur/study/articles.htm The script: hiccupsData <- read.delim("Hiccups.dat", header = TRUE) hiccups<-stack(hiccupsData) names(hiccups)<-c("Hiccups","Intervention")
2016 Jul 27
1
[RFC] One or many git repositories?
On Thu, Jul 28, 2016 at 9:24 AM, Robinson, Paul via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > > -----Original Message----- > > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of > > Justin Lebar via llvm-dev > > Sent: Wednesday, July 27, 2016 1:32 PM > > To: Chris Bieneman > > Cc: llvm-dev at lists.llvm.org > >
2011 Aug 19
0
[LLVMdev] git Status
On Aug 18, 2011, at 10:57 AM, David Greene wrote: > > Did the project ever come to a decision about making a transition to > git? I'm trying to do some longer-term planning and it would be helpful > to know what the roadmap is. Me too. I've been catching up on the thread from a couple weeks ago, and I didn't see any clear conclusion. I have some comments about the
2008 Dec 26
0
Git repository available
Hello, Starting today a public git repository of tinc is available here: http://www.tinc-vpn.org/git/tinc/ It is a conversion from the Subversion repository up to revision 1602 (the release of tinc 1.0.9). The Subversion repository itself was converted from the original CVS repository of tinc, and in the years it had accumulated a lot of cruft. I have removed all branches that were not really
2008 Dec 26
0
Git repository available
Hello, Starting today a public git repository of tinc is available here: http://www.tinc-vpn.org/git/tinc/ It is a conversion from the Subversion repository up to revision 1602 (the release of tinc 1.0.9). The Subversion repository itself was converted from the original CVS repository of tinc, and in the years it had accumulated a lot of cruft. I have removed all branches that were not really
2018 Apr 18
0
Problem with regression line
Hi, Anne, assign Age and Bloodpressure in the correct order to the axes in your call to plot as in: plot(y = Age, x = BloodPressure) abline(SimpleLinearReg1) Hth -- Gerrit --------------------------------------------------------------------- Dr. Gerrit Eichner Mathematical Institute, Room 212 gerrit.eichner at math.uni-giessen.de Justus-Liebig-University Giessen Tel:
2016 Jun 30
6
Sequential ID Git hook
Now that we seem to be converging to an acceptable Git model, there was only one remaining doubt, and that's how the trigger to update a sequential ID will work. I've been in contact with GitHub folks, and this is in line with their suggestions... Given the nature of our project's repository structure, triggers in each repository can't just update their own sequential ID (like
2013 Mar 27
4
[Bug 9744] New: Support Git, Mercurial, Subversion ignore lists
https://bugzilla.samba.org/show_bug.cgi?id=9744 Summary: Support Git, Mercurial, Subversion ignore lists Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: jglick at apache.org
2013 Jul 09
1
Puppet code review - suggestions and options
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
2018 Jan 17
0
effects & lme4: error since original data frame notfoundWASeffects: error when original data frame is missing
Dear Gerrit, This issue is discussed in a vignette in the car package (both for functions in the car and effects packages): vignette("embedding", package="car") . The solution suggested there is the essentially the one that you used. I hope this helps, John ----------------------------- John Fox, Professor Emeritus McMaster University Hamilton, Ontario, Canada Web:
2015 May 23
0
ARI echo test
recreate Echo, if that is possible. trying to recode all dialplan to stasis application > On 22 May 2015, at 19:29, Scott Griepentrog <sgriepentrog at digium.com> wrote: > > Nick- > > Are you wanting to recreate the dialplan Echo() application in stasis? > > Why not just send the call to Echo() instead of Stasis()? > > On Fri, May 22, 2015 at 11:25 AM, Matthew
2011 Sep 01
0
[LLVMdev] git Status Update?
> That's what we need to have a discussion about. If those things will > work for people, great. If not, we have some stuff to figure out. Agreed. Hopefully core peeps will chime in. >> I suppose it's merely a manpower thing now > > I'm not assuming that given the volume of e-mail around this. Sending mail is cheap. Switching to git completely isn't.