similar to: [cfe-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

On 05/01/2020 01:40 PM, Wyatt Childers via llvm-dev wrote: > I agree with everything said here, to me this seems like the most sane option. It seems like this approach could also be tested at a smaller scale if there are concerns about deleting a repo, to see if there is any observable effect. > > While I haven't performed this particular trick on Github, based on my experience

Hello, I want to have the x-axis title of my plot in 2 lines, centered: experiment 1: log2(Ratio H/L) I know that in principle that works with '\n'. However, I am also using the 'substitute' command for my axis title. However, it does not make a new line. What I have so far: logbase <- 2 test <- "bait" cellline <- "cellline" plot(

> Will you be able to start numbering in github at a number larger than the largest bug in bugzilla? It would be annoying to have overlapping bug numbers. Bug numbers exist in code comments, list archives, etc., etc. If someone reads 'clang bug #1234' somewhere it will be ambiguous, which would be a real shame. This won't work in general, unfortunately as there are already a

Hello, I am having trouble specifying a suitable nlme model. My data structure is described by gd <- groupedData(ppath ~ lcut | exp, outer = ~ bait, inner = ~ weight, data = d) i.e. the response (ppath) of several subjects (sub) was measured at levels of a continuous variable (lcut). Subjects were given either of one level of a factor (bait), and all subjects were measured at two levels

> Here are my suggestions for the minimal set of tags: > > + 1 per LLVM backend > + 1 per top-level directory in https://github.com/llvm/llvm-project > > I think if we start here we can create more specialized tags as > GitHub issues gets more traffic and we have more experience using it. The google doc I created contains the slightly cleaned list of current components. It

In some spare time, been trying to get Samba 4.10.6-1 working on AIX. Several earlier posts handled by Louis and Rowland. Which were much appreciated and beneficial. Using this stripped (leaving comments out of it) GLOBALS section of smb.conf: [global] workgroup = boost realm = BOOST.COM server string = Samba Server Version %v interfaces = lo eth0

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:

I have been playing with the cookbook type of tutorials building a fish tournament scoring piece and am having a bit of a problem with a DB field called "points" in my "catch" table that is not input by the user but is calulated based on a "size" field that is input by the user. I have the following in my catch_controller.db def new @catch = Catch.new @fish =

Thanks to you and Louis for your guidance. I really apologize for my lack of knowledge of AD and Samba; and I appreciate your patience and willingness to help. And I apologize for not trimming the reply - don't know how much to retain... The referenced document seems to be leveraging domain services that we're not using. We are only using AD user authentication to access shares on AIX. No

Thanks again for the continued help... Current thinking is using rid for the backend does not place any new administrative functions on the staff - agree? Begs questions of what is being written in smbpasswd, and do we have administrative work on AIX? Such as adding users and a group or two in the range specified for idmap? A mapping "table"? If rid is hands-off administration,

> If we are reasonably certain that no one would be opening new issues on GitHub while the migration is running... And pull requests (the numbering is common for issues and pull requests) as well. And we cannot disable pull requests at all. And I'm afraid the issues will need to be opened as well during the migration. And now the real problem: should an "extra" pull request or

> Can we preserve the existing bug numbers if we migrate this way? There are lots of references to "PRxxxxx" in checked in LLVM artifacts and elsewhere in the world, as well as links to llvm.org/PRxxxxx, and if we can preserve all the issue numbers this would ease the transition pain substantially. Well... I hate to say this, but quite unlikely. Unfortunately, there were significant

I''ve discovered something really weird in rails 1.2.3 (It could be fixed in 2.0? but I don''t know). Recently I started getting the error "Mysql::Error: Lost connection to MySQL server during query" in my application. It seemed like it had popped up almost without relation to anything. There was a page in the RoR wiki with possible solutions but none of them had worked

RedHat 6.0 originally, with upgraded glibc. I just checked the machine again and I was off on the versions. glibc-2.1.3-22 glib-1.2.3-1 glibc-devel-2.1.3-22 Still, pretty similar. As far as I know, those are most recent for RH6. Upgrading the server to 7.x is not exactly easy since it's in co-lo 3 hours away. Plus, until now, I don't think anyone knew Icecast may be effected by this

210 issues have been filed on github so far. That's negligible compared to the total number we have, so a minor additional effort for those seems acceptable if we can't actually clean them out and reuse the numbers. So suppose we start with bugzilla issue #211 and migrate the issues to github one at a time, in order. That would preserve the existing bug numbering and all existing bugs,

Upgraded an AIX Server from AIX 5.3 TL3 with Samba 2.2.7 to AIX 7.1 TL3 with 3.3.12. Client uses AD authentication. Upgrade did not change smb.passwd or smb.conf. Windows users trying to mount a share are presented a request for their credentials; whether they supply the AD or AIX credentials, the access is denied - "Logon failure: unknown user name or bad password." The smbd and

Hello all, Let me say first I'm very new to Linux (only had it running 3 days), so bear with me if I'm a bit ignorant. I'm unsure if I should even post this here, or if this list is exclusively for hardware issues... I'm running into difficulties (on a win2k client) adding the Samba "Domain Admins" group to the Windows "Administrators" group. I am able to log

My apologies (again!) for asking about this old, venerable release. The client is upgrading to 4.10 or 4.11 in early December. The AIX server was joined to a functional Windows 2000 domain in 2015. The AD server has since been upgraded to functional Windows Server 2003 sometime since. They have 2 AD servers - primary is Joe, secondary is Jane. Joe has encountered severe Registry 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:

On Thu, Jan 30, 2020, 10:22 Tom Stellard via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > I want to restart this discussion. There seemed to be support for this, > but we got held up trying to decide on the appropriate set of tags to > use to classify issues. > > I propose that we move forward with this proposal and disable creation of > new bugs in