search for: u999999

...git fetch all the changes from remote origin to local master. 3. Rebase the "test branch" onto the local master. 4. Merge the test branch to master then start building and testing the master branch. 5. If nothing breaks, then I can create a diff file by git show HEAD -U999999 > mypatch.patch from the "master" 6. Upload the patch in the differential and submit for review. Am I missing something? If so, please let me know, it will very helpful for me to start :) If you have any suggestions I would happy to hear from you. LLVM is a fast moving, how often...

...llvm-project increased it to ~1.2GB. Running `git gc --aggressive` brought it down to ~850MB. The worktree of the "master" branch is ~1GB. Adding the Git database gives ~2GB, ~2.2GB, and ~1.9GB. The diff of the proposed staging/apple branch is 3.1MB at `-U0`, 4.1MB at `-U3`, and 32MB at `-U999999` (Phabricator settings). More context We're making a major push over the next few months to upstream changes that have accumulated over time in the branch called "apple/master" at github.com/apple/llvm-project. It has always been a non-goal for us to have changes, but over the year...

On Tue, Jan 7, 2020 at 5:35 PM Jonas Devlieghere <jonas at devlieghere.com> wrote: > On Tue, Jan 7, 2020 at 5:16 PM Bill Wendling via cfe-dev > <cfe-dev at lists.llvm.org> wrote: > > > > On Tue, Jan 7, 2020 at 4:59 PM Doerfert, Johannes <jdoerfert at anl.gov> > wrote: > >> > >> Hi Bill, > >> > >> On 01/07, Bill Wendling

...--aggressive` brought it down to ~850MB. >> - The worktree of the "master" branch is ~1GB. Adding the Git >> database gives ~2GB, ~2.2GB, and ~1.9GB. >> - The diff of the proposed staging/apple branch is 3.1MB at `-U0`, >> 4.1MB at `-U3`, and 32MB at `-U999999` (Phabricator settings). >> >> >> >> *More context* >> >> We're making a major push over the next few months to upstream >> changes that have accumulated over time in the branch called "apple/master" >> at github.com/apple/llvm-project....

...ue: Asterisk1: 2 BRI Cards, TE and NT Mode. - ISDN In (From telco) - ISDN out (to a phone) (Zap/g6) exten => 999999,1,Dial(IAX2/key@asterisk2/999999&Zap/g6/999999) Asterisk2: Just different kind of SIP Connections. exten => 999999,1,Dial(SIP/999999,20,r) exten => 999999,n,Voicemail(u999999) exten => 999999,n,Hangup Now when a call commes in via ISDN on the First Asterisk and both phones are reachable both do ring. The one picked up get's the call. Now when the SIP phone is busy on Asterisk2 the call goes in, Asterisk2 does not know about the other phone ringing on Asterisk...

Hi, One takeaway for me from the recent Phabricator vs Github PR discussions was that arc (arcanist) can be a pain to set up and may pose a hurdle for some contributors. I think those points could be addressed relatively easily by adding a llvm-patch script (or an even better name) that allows users to create and apply patches from reviews.llvm.org using Phabricators API. In my experience, the

I owe you a gala dinner at your favorite restaurant. Really. A few questions: Why did you 'git pull --rebase' when the branch was up-to-date? Is this just a safety habit? I don't understand the pushing upstream. Since we use Phabricator, isn't that the job of the person who commits the patch? Does git keep all my branches up-to-date with the origin? Say I come in tomorrow and