similar to: How soon after the GitHub migration should committing with git-llvm become optional?

Displaying 20 results from an estimated 40000 matches similar to: "How soon after the GitHub migration should committing with git-llvm become optional?"

2019 Oct 15
3
[cfe-dev] How soon after the GitHub migration should committing with git-llvm become optional?
On Tue, Oct 15, 2019 at 3:47 AM Marcus Johnson via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I say retire it instantly. > +1. It has never been a real requirement to use the script. Using native svn is still viable until the point of the migration. > > > On Oct 15, 2019, at 3:14 AM, Tom Stellard via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > > >
2019 Oct 17
3
[cfe-dev] How soon after the GitHub migration should committing with git-llvm become optional?
I'm also a strong proponent of not requiring the wrapper. The linear history piece was important enough to make the cost worth it.  The extra branches piece really isn't.  If someone creates a branch that's not supposed to exist, we just delete it. No big deal.  It will happen, but the cost is so low I don't worry about it. There's a bunch of things in our developer policy
2019 Oct 10
4
[cfe-dev] GitHub Migration Schedule and Plans
On 10/09/2019 11:05 PM, Mehdi AMINI wrote: > > > On Wed, Oct 9, 2019 at 10:16 PM Tom Stellard via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote: > > Hi, > > We're less than 2 weeks away from the developer meeting, so I wanted to > give an update on the GitHub migration and what's (hopefully) going to >
2019 Mar 17
1
lda: Unknown mail storage driver maildir
hi all, I have a successful (self-compiled from source code) Dovecot v2.2.16 setup active on my Solaris-10 server, with mails stored in user's $HOME/Maildir The mails are fetched from the ISP with "fetchmail", using a "cron" job fetchmail -f $HOME/etc/pop3.myisp where the file "$HOME/etc/pop3.myisp" contains set logfile fetchmail.log poll pop.myisp.be with
2019 Jan 29
13
[Github] RFC: linear history vs merge commits
Hi, As part of the migration of LLVM's source code to github, we need to update our developer policy with instructions about how to interact with the new git repository. There are a lot of different topics we will need to discuss, but I would like to start by initiating a discussion about our merge commit policy. Should we: 1. Disallow merge commits and enforce a linear history by
2007 Mar 09
2
Is there any variable for Voicemail Password in Asterisk
Hi guys This is my Ist post on this group. Is there any variable like ($VM_CALLERID for voicemail mailbox) for accessing Asterisk Voicemail password which is set through comedian mail.?????????????? plz reply me as soon as possible.... <html><div><PRE class=quote><IMG height=2 src="http://graphics.hotmail.com/greypixel.gif" width="100%"
2016 May 09
5
[cfe-dev] [Openmp-dev] RFC: Proposing an LLVM subproject for parallelism runtime and support libraries
I talked to Chandler about the name "offload_libs" vs "parallel_libs" and he said he thinks "offload" is too narrow of a term for the scope he sees for this subproject. One example he brought up was AVX 512. He thinks that code explicitly targeting CPU parallelism should also be included in this project, even though it doesn't fit in the category of
2020 Feb 04
4
How to distinguish between user defined function in a program and library functions
Say, I have the following program:    #include <iostream>    int main(){      std::cout << "hello\n";      return 0;    } After generating llvm bitcode using the following command:       $ clang++ -c -emit-llvm -O -Xclang -disable-llvm-passes a.cpp the bitcode has the following function with define. __cxx_global_var_init    main   
2019 Mar 19
8
[GitHub] RFC: Enforcing no merge commit policy
Hi, I would like to follow up on the previous thread[1], where there was a consensus to disallow merge commits in the llvm github repository, and start a discussion about how we should enforce this policy. Unfortunately, GitHub does not provide a convenient way to fully enforce this policy. We can enforce it for pull requests, but not for direct pushes to the master branch, so we will have to
2019 Oct 10
3
[cfe-dev] GitHub Migration Schedule and Plans
On Thu, Oct 10, 2019 at 1:14 PM Jordan Rupprecht <rupprecht at google.com> wrote: > > > On Thu, Oct 10, 2019 at 12:29 PM Tom Stellard via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> On 10/10/2019 11:40 AM, Mehdi AMINI wrote: >> > >> > >> > On Thu, Oct 10, 2019 at 10:59 AM Tom Stellard <tstellar at redhat.com >>
2019 Oct 10
3
[cfe-dev] GitHub Migration Schedule and Plans
On 10/10/2019 11:40 AM, Mehdi AMINI wrote: > > > On Thu, Oct 10, 2019 at 10:59 AM Tom Stellard <tstellar at redhat.com <mailto:tstellar at redhat.com>> wrote: > > On 10/09/2019 11:05 PM, Mehdi AMINI wrote: > > > > > > On Wed, Oct 9, 2019 at 10:16 PM Tom Stellard via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at
2016 Apr 26
3
PPC little endian?
Hi, I am wondering why we dont support PPC32 LE? Here is the output of llvm-mc --version, in which only PPC32, PPC64 & PPC64LE are supported. $ llvm-mc --version LLVM (http://llvm.org/): LLVM version 3.6.2 Optimized build with assertions. Built Aug 2 2015 (11:39:46). Default target: x86_64-apple-darwin15.4.0 Host CPU: core-avx2 Registered Targets: aarch64 - AArch64
2019 Mar 20
5
[cfe-dev] [lldb-dev] [GitHub] RFC: Enforcing no merge commit policy
Excuse my ignorance (I'm not great with Git) but how would it differ for workflows of people who use a Git repository for local work but still use `svn up + patch + svn commit <list of files>` to actually land post CR or for NFC patches, while resolving conflicts during a pull into a local (non-trunk) branch manually, after the eventual full switch to GitHub? I'm aware that SVN
2013 Feb 12
2
ix? / Intel(R) PRO/10GbE
I finally got a 10G card that is recognized by FreeBSD (9.1-stable): ... ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.4.8> port 0xecc0-0xecdf mem 0xd9e80000-0xd9efffff,0xd9ff8000-0xd9ffbfff irq 40 at device 0.0 on pci4 ix0: Using MSIX interrupts with 9 vectors ix0: RX Descriptors exceed system mbuf max, using default instead! ix0: Ethernet address: 90:e2:ba:29:c0:54
2019 Mar 20
2
[cfe-dev] [lldb-dev] [GitHub] RFC: Enforcing no merge commit policy
It sounds like we need to get someone from the Foundation (chandlerc@, lattner@, tanya@, someone else?) to reach out to them offline about this. On Wed, Mar 20, 2019 at 11:23 AM Arthur O'Dwyer <arthur.j.odwyer at gmail.com> wrote: > On Wed, Mar 20, 2019 at 2:19 PM Tom Stellard via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> On 03/20/2019 10:41 AM, Zachary
2020 Mar 17
2
[cfe-dev] RFC: Switching from Bugzilla to Github Issues
On 03/16/2020 11:09 PM, Roman Lebedev wrote: > On Tue, Mar 17, 2020 at 6:07 AM Tom Stellard via cfe-dev > <cfe-dev at lists.llvm.org> wrote: >> >> On 03/16/2020 10:13 AM, Florian Hahn wrote: >>> Hi, >>> >>>> On Mar 16, 2020, at 14:43, Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
2018 Feb 23
4
Stale mailbox lock file
Hi all, I would like to understand the meaning of "Stale mailbox lock file detected" In index-storage.c (https://mis.dopa.go.th/atmail/server_source/dovecot/src/lib-storage/index/index-storage.c) there is this notice "Stale mailbox lock file detected" ... I have a java application which connects via javamail to a dovecot server and I have some anomalies when that message
2020 Mar 17
2
[cfe-dev] RFC: Switching from Bugzilla to Github Issues
On 03/17/2020 06:39 AM, Roman Lebedev wrote: > On Tue, Mar 17, 2020 at 4:35 PM Tom Stellard <tstellar at redhat.com> wrote: >> >> On 03/16/2020 11:09 PM, Roman Lebedev wrote: >>> On Tue, Mar 17, 2020 at 6:07 AM Tom Stellard via cfe-dev >>> <cfe-dev at lists.llvm.org> wrote: >>>> >>>> On 03/16/2020 10:13 AM, Florian Hahn wrote:
2020 Mar 20
2
[cfe-dev] [lldb-dev] RFC: Switching from Bugzilla to Github Issues
Please can we shut down one of the two systems for new bugs ASAP? We've already had an instance of someone filing the same bug using both systems, with two different fixes being committed by two different people at the same time... On Tue, 17 Mar 2020 at 06:49, Robinson, Paul via cfe-dev < cfe-dev at lists.llvm.org> wrote: > > > > -----Original Message----- > > From:
2020 Mar 17
4
[cfe-dev] RFC: Switching from Bugzilla to Github Issues
On 03/16/2020 10:13 AM, Florian Hahn wrote: > Hi, > >> On Mar 16, 2020, at 14:43, Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> I've also implemented a notification system using GitHub actions that will make >> it possible to subscribe to individual issue tags, so we would enable this on Monday