search for: monolith

I have one reasone why we should not moe to monolithic repository - If you do some light stuff like clang-tidy, that don't often require syncing with clang, but you still want to have the most recent checks, then I don't see a solution in monolithic repository. And this is a real issue if you only have 2 or 4 core laptop to do work. And I gue...

...changes, then switch to a new branch based on tip of head and make some new changes. Finally you want to switch back to your original branch. And when you switch between branches, you want to get an llvm that's in sync with the clang in your working copy. Here's how I'd do it with a monolithic git repository, option (b): git commit # old-branch git fetch git checkout -b new-branch origin/master # hack hack hack git commit # new-branch git checkout old-branch Here's how I'd do it with option (a), submodules. I've used git -C here to make it explicit which repo...

I spun a new xen kernel from pristine sources using modules, had the APCI errors and scsi timeouts. I took pristine source and spun a monolithic kernel and everything appears to be working. gcc version 3.4.4 20050721 (Red Hat 3.4.4-2) if it matter. xen_changeset : Wed Oct 26 11:59:13 2005 +0100 7500:20d1a79ebe31 I have had this APCI issue on this SMP Athlon with modules for a while now. Guess I will stick with monolithic kernels for...

...traffic repo and > start looking for alternatives. At that point I think we'll end up switching > to pull requests and accepting non-linear history. Similarly, I think the > desire for incremental revision numbers will gradually fade as people get > used to git. This is valid on a monolithic model, and that is one of the reasons I prefer it. Today, I personally prefer the Git model (merges, pull requests, fuzzy history), but I haven't always done so. The more I learnt how to use Git, the more I realised how valuable the "confusing model" is for distributed development....

...d also drain my battery. So basically what happens is you pay for what you don't use, which is not C++ way :P > > 2016-07-22 13:18 GMT-07:00 Piotr Padlewski <piotr.padlewski at gmail.com <mailto:piotr.padlewski at gmail.com>>: > I have one reasone why we should not moe to monolithic repository - If you do some light stuff like clang-tidy, that don't often require syncing with clang, but you still want to have the most recent checks, then I don't see a solution in monolithic repository. > And this is a real issue if you only have 2 or 4 core laptop to do work. &gt...

...that you need to check out. I guess you could find the upstream parent of your branch, get the SVN revision number from the commit message, then go to the LLVM branch and find a commit which has an SVN number that's nearby? This would all become as simple as "git checkout" under the monolithic model. On Thu, Jul 21, 2016 at 9:16 AM, Justin Lebar <jlebar at google.com> wrote: >> Our clones of LLVM and clang have a reasonable amount of history (a couple of hundred commits, I believe), including multiple branches, that we’d want to preserve. Both branches have merged from up...

Hi, All ! I'm trying to use nut 2.0.5 on FreeBSD 4.11-STABLE with UPS INELT Monolith II 1000LT UPS connected to box with RS-232 cable. In ups.conf: [apc] driver = megatec port = /dev/cuaa1 desc = "UPS" When starting /usr/local/etc/rc.d/nut.sh start got: Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - Megatec protocol driver 1.5 (2.0.5) Carlos Ro...

I guess perl 5.18 was released and it is causing issues texi2html -monolithic -number-sections qemu-doc.texi texi2html -monolithic -number-sections qemu-tech.texi /data/dev/xen/xen-4.3-git/src/xen-build/tools/qemu-xen-traditional-dir/ texi2pod.pl qemu-doc.texi qemu.pod pod2man --section=1 --center=" " --release=" " qemu.pod > qemu.1 qemu.pod around l...

I guess perl 5.18 was released and it is causing issues texi2html -monolithic -number-sections qemu-doc.texi texi2html -monolithic -number-sections qemu-tech.texi /data/dev/xen/xen-4.3-git/src/xen-build/tools/qemu-xen-traditional-dir/ texi2pod.pl qemu-doc.texi qemu.pod pod2man --section=1 --center=" " --release=" " qemu.pod > qemu.1 qemu.pod around l...

I have a data frame with three columns, type (a factor with two values: "Monolithic" and "Compositional"), size (numeric), and states (numeric). I want to create a plot where size goes on the x-axis and states goes on the y-axis. In this plot, I want two lines, one where the type is "Monolithic" and one where the type is "Compositional". I t...

> Which projects do we put under this monolithic repository? The proposal at the moment is to include llvm, clang, clang-tools-extra, lld, polly, lldb, llgo, compiler-rt, openmp, and parallel-libs. This is the set {llvm} plus the transitive closure of "projects that are version-locked to a project in the set", where the closure i...

On Friday, 10 January 2020 15:05:33 CET Richard W.M. Jones wrote: > libguestfs usually needs qemu. However it only requires an emulator > for the same architecture, not for all architectures. > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > architectures, as well as a bunch of other stuff we don't need at all > like network interface support and nwfilter.

On Fri, Jan 10, 2020 at 02:05:33PM +0000, Richard W.M. Jones wrote: > libguestfs usually needs qemu. However it only requires an emulator > for the same architecture, not for all architectures. > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > architectures, as well as a bunch of other stuff we don't need at all > like network interface support and nwfilter.

On Fri, Jan 10, 2020 at 02:26:35PM +0000, Richard W.M. Jones wrote: > On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > > Do you use the libvirt "secret" APIs at all (disk encryption, network > > disk auth passwords) ? If so you will need "libvirt-daemon-driver-secret" > > too. How about any other libvirt sub-driver APIs ? Networking ?

libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. --- libguestfs.spec

libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. --- libguestfs.spec

On Friday, 10 January 2020 17:34:27 CET Daniel P. Berrangé wrote: > > > > virStoragePoolFree ( > > > > virStoragePoolGetInfo ( > > > > virStoragePoolLookupByName ( > > > > virStorageVolFree ( > > > > virStorageVolGetInfo ( > > > > virStorageVolGetPath ( > > > > virStorageVolLookupByName ( > > > > >

Monolithic is trying to solve the wrong problem - it's that simple. Any discussion or attempt to coddle those who think it's necessary is a waste of time. #dictator As part of any potential migration, everyone involved must start to accept certain changes, (large or small) to the workflow. The big...

On Fri, Jan 10, 2020 at 05:21:23PM +0100, Pino Toscano wrote: > On Friday, 10 January 2020 15:39:21 CET Daniel P. Berrangé wrote: > > On Fri, Jan 10, 2020 at 02:26:35PM +0000, Richard W.M. Jones wrote: > > > On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > > > > Do you use the libvirt "secret" APIs at all (disk encryption, network >

Thanks for the update Andy. I'm very happy to be involved in anyway that is helpful. If you would like me to test ideas, or contribute to further discussions, then please let me know. I currently have extempore running nicely with MCJIT for the "monolithic" case and am working on various LLVM hacks to better understand the issues involved with non-monolithic approaches - in particular I'm starting with your multi-module approach. I will report back when (and if) I have something useful to contribute. Cheers, Andrew. On Wed, Feb 6, 2013...