similar to: Status of the git.llvm.org git repos

My expectation was that they would continue to be fed from the updates to the svn repo. But again, I don't recall where I got that impression from. It may have been a bad assumption on my part. Tom. From: Anton Korobeynikov <anton at korobeynikov.info> Sent: Tuesday, February 25, 2020 12:36 PM To: Tom Honermann <thonerma at synopsys.com> Cc: llvm-dev at lists.llvm.org; Michael

> On Oct 13, 2016, at 11:56 AM, Renato Golin <renato.golin at linaro.org> wrote: > > Hi Duncan, > > I don't understand your concerns. > > First, the choice between sub-modules and mono-repo has been put > forward as the only two choices because people felt that, if we let it > open, we'd have too many different implementation details and we'd >

Hello, I was wondering what was the current expected practice for committing patches to LLVM now that the Git monorepo is here. I have commit access to SVN but when I try to land my patched through GitHub I get an error saying "Permission to llvm/llvm-project.git denied". Depending on the answer, the documentation might need to be slightly clarified: the getting started documents for

Hello. I'm developing a LLVM based project and I'm using a fork of LLVM and Clang repos from https://github.com/llvm-mirror . The workflow was merging my work with release_XX branches from these repos, so now I have my commits interspersed with upstream ones. I'd be grateful for any advice on how should I move my work towards official git monorepo. I want to preserve my history, of

Here's another question about the current status of this. It's close to two months after the official monorepo was supposed to be published. Can someone give an update? Is this on hold indefinitely? Are there concrete issues that people are working on and this will happen as soon as those are resolved? At the least, I'm assuming the "SVN will shut down 1 year from now"

What's the status here? Can someone keep https://llvm.org/docs/Proposals/GitHubMove.html updated with the current status of things? And once things are usable, probably update https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo as well. On Wed, Oct 24, 2018 at 4:57 AM Jacob Carlborg via lldb-dev < lldb-dev at lists.llvm.org> wrote: > On 2018-10-24

It'd be nice to know what about our repository is breaking it. Do they have any idea what that is? For example -- I think that we probably will want to archive+discard many of the random branches and tags currently in the repository. If the large number of branches and tags is breaking it, then maybe it just starts working after we do so. On Thu, Nov 8, 2018 at 3:53 PM Anton Korobeynikov

On 10/11/2018 03:27 PM, James Y Knight via llvm-dev wrote: > TLDR: https://github.com/llvm-git-prototype/ exists as a read-only mirror of SVN, and is being updated continuously with a script running on an llvm-project AWS VM. > Hi James, What is the current status of the monorepo, have you resolved all the known issues with the history? Are there any other changes that need to be made

Hi all In case anyone has a remote to the (unofficial) https://github.com/llvm-mirror, please note that all the repos are at least 8 days behind. There's no warning about it. The page still says it's "Updated every five minutes". Best Stefan -- https://flowcrypt.com/pub/stefan.graenitz at gmail.com

Isn’t the checkout a local operation that should not involved GitHub ? Did you mean the clone operation ? And about sparse-checkout, I though they require a full clone of the repository anyway. Is there a way to do a partial clone only ? Note: If you don’t need the whole history local, you may perform a swallow clone (using —depth 1). > Le 9 nov. 2018 à 01:02, Anton Korobeynikov via llvm-dev

On Fri, Nov 16, 2018 at 4:04 PM NAKAMURA Takumi <geek4civic at gmail.com> wrote: > Hello, David. > > On Sat, Nov 17, 2018 at 7:46 AM David Jones via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi James, >> >> I've started working with the prototype layout in context of Google's >> internal infrastructure. With deep apologies, I

> On 2016-Sep-18, at 09:51, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Folks, > > After feedback from Chris and Mehdi, I have added one long text answer > to *each* critical questions (impact on productivity), so that people > can extend their reasoning. > > But I have not made them compulsory, so that people that don't know > much

Hi James, I've started working with the prototype layout in context of Google's internal infrastructure. With deep apologies, I have a (very late, I know) pair of requests that have only recently solidified for me. 1. Could you add annotated tags after the cut point of each release? (I think this would probably be easy.) 2. Could you mark branch/tag operations somehow other than a

[ I am initially copying only a few lists since they seem like the most impacted projects and I didn't want to spam all the mailing lists. Please let me know if other lists should be included. ] I submitted D68230 for review but this is not about that patch per se. The patch allows update_cc_test_checks.py to process tests that should check target asm rather than LLVM IR. We use this

On 6/29/2016 10:03 AM, Renato Golin via cfe-dev wrote: > Since the umbrella project cannot see the sub-modules' commits without > some form of update, there are two ways to do this: > > P. Per push: Every push (not commit) on all other repositories will > trigger a hook that will hit a URL on our server, telling it to > generate an incremental ID, update some umbrella's

On 10/16/2019 12:02 PM, Roman Lebedev wrote: > On Wed, Oct 16, 2019 at 9:55 PM Tom Stellard <tstellar at redhat.com> wrote: >> >> On 10/16/2019 07:31 AM, Roman Lebedev wrote: >>> +1, please. >>> >>> Also, putting a tag on the *first* commit in the repo, >>> and doing `git describe --match FIRST_COMMIT_TAG` will be *great*! >>>

Hi, > On Sep 7, 2016, at 10:30 AM, dag at cray.com wrote: > > Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> writes: > >> Right, we actually have a proposal to take what is in the current SVN >> repo here: http://llvm.org/svn/llvm-project/ and migrate this to a >> single repository. >> I was not sure if you were referring to this proposal

Hi Eric, Old flang certainly uses C-style strings but f18 uses std::string with few exceptions. Most of the instances in f18 of “char *” aren’t really strings in the C sense – they’re not null terminated and are really just pointers into raw or cooked source files/streams. I can’t think of an instance where the compiler dynamically allocates an array of characters and uses it as a C string. -

On 29 June 2016 at 16:50, Tom Honermann <Thomas.Honermann at synopsys.com> wrote: > How would you coordinate dependent updates to the sub-modules? We won't. Not now. Maybe later. Right now, doing that means changing how we work and we're trying to make the least number of changes at a time. But this is the most requested feature and I'm sure we'll find something that

On Tue, Feb 12, 2019 at 11:05 AM Jonas Devlieghere via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Tue, Feb 12, 2019 at 10:54 AM Kostya Serebryany <kcc at google.com> wrote: > >> >> >> On Tue, Feb 12, 2019 at 10:45 AM Jonas Devlieghere <jonas at devlieghere.com> >> wrote: >> >>> Hi Kostya, >>> >>> I remember