search for: worktrees

On Tue, Nov 13, 2012 at 6:02 PM, Ramkumar Ramachandra <artagnon at gmail.com> wrote: > Add several .gitignore rules to various directories to ensure a clean > worktree after a default build. Hi, These gitignore lists require maintenance. Is is possible to express the same set of filenames as patterns like '*.inc' in the root gitigrore file, so that adding/removing a new

Hi Dmitri, Dmitri Gribenko wrote: > On Tue, Nov 13, 2012 at 6:02 PM, Ramkumar Ramachandra > <artagnon at gmail.com> wrote: >> Add several .gitignore rules to various directories to ensure a clean >> worktree after a default build. > > Hi, > > These gitignore lists require maintenance. Is is possible to express > the same set of filenames as patterns like

On Nov 13, 2012, at 8:34 AM, Ramkumar Ramachandra <artagnon at gmail.com> wrote: > Hi Dmitri, > > Dmitri Gribenko wrote: >> On Tue, Nov 13, 2012 at 6:02 PM, Ramkumar Ramachandra >> <artagnon at gmail.com> wrote: >>> Add several .gitignore rules to various directories to ensure a clean >>> worktree after a default build. >> >> Hi,

> I was under the impression that in-source-tree builds were an unsupported > configuration. It's certainly strongly discouraged. I'm not fond of the > idea of making it easier, especially when there's a maintenance cost to > doing so. > Strongly discouraged, and yes, this. -eric -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Tue, Nov 13, 2012 at 12:04 PM, Eric Christopher <echristo at gmail.com> wrote: >> I was under the impression that in-source-tree builds were an unsupported >> configuration. It's certainly strongly discouraged. I'm not fond of the idea >> of making it easier, especially when there's a maintenance cost to doing so. > > Strongly discouraged, and yes,

Chandler Carruth wrote: > FWIW, if in-tree builds work for CMake, I consider that a bug and will fix it. How else am I supposed to build LLVM? I ran the toplevel configure and make script. Ram

Add several .gitignore rules to various directories to ensure a clean worktree after a default build. Signed-off-by: Ramkumar Ramachandra <artagnon at gmail.com> --- Just cloned and built LLVM. This annoyed me. Here's a trivial patch. .gitignore | 10 ++++++++++ bindings/ocaml/llvm/.gitignore | 1 + docs/.gitignore

There are huge differences between source files in the version 3.0.9 released as a tar.gz and source files in git. I would assume that the released version would correspond to the version in git but with 3.0.9 it is not like that. In 3.1.0 the released and git versions are more or less the same. So my question is, from what source files was the 3.0.9 version created? Thank you. Regards, Michal

On 31 May 2016 at 21:28, Mehdi Amini <mehdi.amini at apple.com> wrote: > Ideally, I'd prefer the cross-repository to be handled with an extra layer, in a way similar as described in: https://gerrit-review.googlesource.com/Documentation/user-submodules.htm (somehow conceptually similar to Android manifests XML files). > It would be easy to have tooling/scripts for llvm that would

On Tue, Apr 04, 2017 at 11:12:11AM +0200, Michal Ruprich via rsync wrote: > There are huge differences between source files in the version 3.0.9 > released as a tar.gz and source files in git. I would assume that the > released version would correspond to the version in git but with 3.0.9 > it is not like that. In 3.1.0 the released and git versions are more or > less the same. How

> Today I *can* checkout only LLVM and Clang. On a single Git repo I can't. This is true if you s/checkout/clone/. With a single repo, you must clone (download) everything (*), but after you've done so you can use sparse checkouts to check out (create a working copy of) only llvm and clang. So you should only notice the fact that there exist things other than llvm and clang when you

On 22 July 2016 at 13:48, Piotr Padlewski via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> The build system can help, you just need to have two (sparse) checkout: one for LLVM/clang and the other for clang-tidy, and configure the build with the LLVM/clang checkout adding the clang-tidy as external. > Can you describe it more? Something like this $ git clone git at

On 13 December 2016 at 17:45, Zachary Turner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Over a month ago I submitted some patches to begin documenting PDB file > format. These files are in llvm/docs/PDB. When I view the docs online > though, they appear stale. Many of the pages are blank, containing only a > file header. This matches up with my initial commit of the

> On May 31, 2016, at 1:31 PM, Renato Golin <renato.golin at linaro.org> wrote: > > On 31 May 2016 at 21:28, Mehdi Amini <mehdi.amini at apple.com> wrote: >> Ideally, I'd prefer the cross-repository to be handled with an extra layer, in a way similar as described in: https://gerrit-review.googlesource.com/Documentation/user-submodules.htm (somehow conceptually

To facilitate collaboration on an upstreaming effort (see "More context" below), we'd like to push a branch (with history) called "staging/apple" to github.com/llvm/llvm-project to serve as an official contribution to the LLVM project. This enables motivated parties to work with us to craft incremental patches for review on Phabricator. This branch would live during the

> On Jul 20, 2016, at 5:56 PM, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 21 July 2016 at 01:39, Justin Lebar <jlebar at google.com> wrote: >> This is true if you s/checkout/clone/. With a single repo, you must >> clone (download) everything (*), but after you've done so you can use >> sparse checkouts to check out (create a

Hi, In our CMake build system there are currently two ways of specifying which LLVM sub projects to build by setting CMake cache variables. * Setting `LLVM_ENABLE_PROJECTS` to the list of projects to enable (e.g. `-DLLVM_ENABLE_PROJECTS=clang;compiler-rt`) * Setting `LLVM_TOOL_<PROJECT>_BUILD` boolean CMake cache variables (e.g. `-DLLVM_TOOL_CLANG_BUILD=ON

On Mon, Jun 29, 2020 at 9:43 PM Mehdi AMINI via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hey Duncan, > > On Mon, Jun 29, 2020 at 8:28 PM Duncan Exon Smith via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> To facilitate collaboration on an upstreaming effort (see "More context" >> below), we'd like to *push a branch* (with history)

>> 3. For many (most?) developers, changing to a monolithic git repo is a >> *bigger* workflow change than switching to separate git repos. Many >> people (and at least some downstream infrastructure) use the git >> mirrors exclusively, aside from git-svn for committing. >> >> I believe the idea is to continue to maintain the read-only independent >> git

I just got a Diffusion notification about a change of mine being reverted by Fangrui, but I'm not sure that's actually what happened and am confused and concerned. My commit was "[DebugInfo] Allow spill slots in call site parameter descriptions", and it appears in the history under two hashes: 1ee84e and 67c416. The first commit contains the actual change. The second touches