search for: githubmov

...on point with respect to the document, neither too much or not enough. If the survey does not help quantifying how much a concern raised in the proposal is important, it is an issue to me. For this particular question, here are some relevant pieces of the proposal: http://llvm.org/docs/Proposals/GitHubMove.html#concerns <http://llvm.org/docs/Proposals/GitHubMove.html#concerns> "Refactoring across projects is not friendly: taking some functions from clang to make it part of a utility in libSupport wouldn’t carry the history of the code in the llvm repo, …. “ http://llvm.org/docs/Proposals...

...t a possible move of our hosting to Git/GitHub, and consider the various options and associated tradeoff (Schedule entry here: http://sched.co/8Yzj <http://sched.co/8Yzj> ) I’d like to remind you that the detail of the proposals and the variants is online here: http://llvm.org/docs/Proposals/GitHubMove.html <http://llvm.org/docs/Proposals/GitHubMove.html> ; and that a survey is opened here: https://goo.gl/forms/ZYs0Wv9g0w0ikCRQ2 <https://goo.gl/forms/ZYs0Wv9g0w0ikCRQ2> Please fill the survey if you haven’t yet! If you answer the survey to represent your company position, I invite y...

> 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 >

...the (read-only) svn repo? We had not planned to complete our own transition to the mono repo until a little later this year, but if these repos are no longer maintained, we'll have to readjust our priorities. I'm aware of the guidance on how to transition (https://llvm.org/docs/Proposals/GitHubMove.html#moving-local-branches-to-the-monorepo) and am not seeking any advice on how to do so. Tom. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200225/3a7aa6d9/attachment.html>

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: > O...

...GitHub Move Proposal [2] reads "a GitHub account will be required instead of SVN username/password-hash". In that last sentence, is the future tense still applicable? Thanks, Marco [1] http://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access [2] https://llvm.org/docs/Proposals/GitHubMove.html#what-this-proposal-is-not-about IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpo...

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

...ddressed at all. Though > they are aware that this is the issue for us. > On Thu, Nov 8, 2018 at 12:53 PM Nico Weber via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > > > 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-d...

...at this is the issue for us. >>> On Thu, Nov 8, 2018 at 12:53 PM Nico Weber via llvm-dev >>> <llvm-dev at lists.llvm.org> wrote: >>>> >>>> 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 Carl...

...vn repo? We had not planned to complete our own transition to the mono repo until a little later this year, but if these repos are no longer maintained, we'll have to readjust our priorities. > > > > I'm aware of the guidance on how to transition (https://llvm.org/docs/Proposals/GitHubMove.html#moving-local-branches-to-the-monorepo) and am not seeking any advice on how to do so. > > > > Tom. > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org> > https://list...

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

...locking, and if it is if there's a plan for it. Thanks Nico On Sat, Oct 20, 2018 at 4:10 AM Jonas Hahnfeld via cfe-dev < cfe-dev at lists.llvm.org> wrote: > (+openmp-dev, they should know about this!) > > Recapping the "Concerns" > (https://llvm.org/docs/Proposals/GitHubMove.html#id12) there is a > proposal of "single-subproject Git mirrors" for people who are only > contributing to standalone subprojects. I think this will be easy in the > transition period, we can just continue to move the current official git > mirrors. Will this "service...

...LLDB Dev <lldb-dev at lists.llvm.org> Subject: Re: [llvm-dev] [cfe-dev] Mailing list changes this week I thought we were just going to count commits on a particular branch and use the (branch name, commit count) tuple as our monotonic incrementing identifier? https://llvm.org/docs/Proposals/GitHubMove.html#on-managing-revision-numbers-with-git From: cfe-dev <cfe-dev-bounces at lists.llvm.org<mailto:cfe-dev-bounces at lists.llvm.org>> on behalf of cfe-dev <cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>> Organization: Red Hat Reply-To: "tstellar at redh...

...>> Subject: Re: [llvm-dev] [cfe-dev] Mailing list changes this week >> >> >> >> I thought we were just going to count commits on a particular branch and use the (branch name, commit count) tuple as our monotonic incrementing identifier? https://llvm.org/docs/Proposals/GitHubMove.html#on-managing-revision-numbers-with-git >> >> >> >> >> >> From: cfe-dev <cfe-dev-bounces at lists.llvm.org> on behalf of cfe-dev <cfe-dev at lists.llvm.org> >> Organization: Red Hat >> Reply-To: "tstellar at redhat.com" <t...

On 10/15/2019 09:44 PM, Mehdi AMINI wrote: > > > On Tue, Oct 15, 2019 at 9:33 PM Tom Stellard <tstellar at redhat.com <mailto:tstellar at redhat.com>> wrote: > > On 10/15/2019 09:24 PM, Mehdi AMINI wrote: > > Hi Tom. > > > > One issue with this is that we don't have a clear "ordering" from linear revision numbers from

...ion, including branches. I've also converted a bunch of the auxiliary repositories. > > I would request that other people help take charge of the remainder of the work. Most importantly -- making a plan for implementing the *rest* of the migration. We have https://llvm.org/docs/Proposals/GitHubMove.html, but I think it'll need significant fleshing out and updating. I'm happy to assist with the rest of the migration, but I'd like to _not_ be primarily responsible for other parts beyond svn->git repository conversion. > > Some things that could be discussed in such a plan...

...] [cfe-dev] Mailing list changes this week >>>> >>>> >>>> >>>> I thought we were just going to count commits on a particular branch and use the (branch name, commit count) tuple as our monotonic incrementing identifier? https://llvm.org/docs/Proposals/GitHubMove.html#on-managing-revision-numbers-with-git >>>> >>>> >>>> >>>> >>>> >>>> From: cfe-dev <cfe-dev-bounces at lists.llvm.org> on behalf of cfe-dev <cfe-dev at lists.llvm.org> >>>> Organization: Red Hat &gt...

...es. >>>> > >>>> > I would request that other people help take charge of the remainder >>>> of the work. Most importantly -- making a plan for implementing the *rest* >>>> of the migration. We have >>>> https://llvm.org/docs/Proposals/GitHubMove.html, but I think it'll >>>> need significant fleshing out and updating. I'm happy to assist with the >>>> rest of the migration, but I'd like to _not_ be primarily responsible for >>>> other parts beyond svn->git repository conversion. >>&g...

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

...lso converted a bunch of the auxiliary repositories. >> > >> > I would request that other people help take charge of the remainder of >> the work. Most importantly -- making a plan for implementing the *rest* of >> the migration. We have https://llvm.org/docs/Proposals/GitHubMove.html, >> but I think it'll need significant fleshing out and updating. I'm happy to >> assist with the rest of the migration, but I'd like to _not_ be primarily >> responsible for other parts beyond svn->git repository conversion. >> > >> > Some t...