search for: release_1

I.e., I see this when I run `git fetch`: ``` $ git fetch -v llvm.org From http://llvm.org/git/llvm = [up to date] master -> llvm.org/master = [up to date] release_1 -> llvm.org/release_1 = [up to date] release_16 -> llvm.org/release_16 = [up to date] release_20 -> llvm.org/release_20 = [up to date] release_21 -> llvm.org/release_21 = [up to date] release_22 -> llvm.org/release_22 = [up to date] release_23 -> llv...

...control system for all the >> llvm projects is svn, I'd just as soon use svn as the tool at my end. > The git mirrors only contain what's in trunk in the SVN repos. I think it contains branches of several previous releases: $ git branch -r llvm-upstream/master llvm-upstream/release_1 llvm-upstream/release_16 llvm-upstream/release_20 llvm-upstream/release_21 llvm-upstream/release_22 llvm-upstream/release_23 llvm-upstream/release_24 llvm-upstream/release_25 llvm-upstream/release_26 llvm-upstream/release_27 llvm-upstream/release_28 llvm-upstream/release_29...

...2016 at 5:34 PM, Duncan P. N. Exon Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I.e., I see this when I run `git fetch`: > ``` > $ git fetch -v llvm.org > From http://llvm.org/git/llvm > = [up to date] master -> llvm.org/master > = [up to date] release_1 -> llvm.org/release_1 > = [up to date] release_16 -> llvm.org/release_16 > = [up to date] release_20 -> llvm.org/release_20 > = [up to date] release_21 -> llvm.org/release_21 > = [up to date] release_22 -> llvm.org/release_22 > = [up to date]...

On 2011-08-29 04:21, Kurt Lidl wrote: > While I agree bootstrapping a new mirror from scratch is time and > resource consuming, this can be largely avoided by making a seed > of the svn tree available. (Basically, I think that looks like > a compressed tar file of the svn repository.) Or, a svnadmin dump > of the repo could be made available for the adventurous. Having the same

...ied something like this but it breaks due to the restrictions: git svn init --stdlayout https://<user>@llvm.org/svn/llvm-project/llvm \ --ignore-paths="^.*(Apple|PowerPC.*|SVA|eh-experimental|ggreif|non-call-eh|parallel|release_.*|vector_llvm|wendling|May2007|checker|cremebrulee|start|RELEASE_1.*|RELEASE_2[0-7])" Obviously, replace <user> with whatever it needs to be to allow dcommit to work. Ideally we'd have clang and llvm-gcc git mirrors as well via the --prefix argument to git-svn init, but let's not get ahead of ourselves. :) It appears that there's not much...

Matthieu, On Tue, Mar 1, 2011 at 8:02 AM, Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> wrote: > At some point in the past, an anti-git-svn system had been set up on > llvm.org. Has this been disabled since? I don't manage to do much with > git-svn: Maybe sure. Anton said it is disabled to access upper directories with svn. Thus, we (accessing llvm.org remotely) cannot do

On Wed, Aug 17, 2011 at 01:47:02PM -0700, Benjamin Kramer wrote: > On 17.08.2011, at 11:36, Kurt Lidl <lidl at pix.net> wrote: > > > Why can't I mirror the whole tree? > > The original reason for this limitation was that complete checkouts > put a lot of stress on the server. While I agree bootstrapping a new mirror from scratch is time and resource consuming,

...repository > directory. Surely not (at the server) > git svn init --stdlayout https://<user>@llvm.org/svn/llvm-project/llvm \ >  --ignore-paths="^.*(Apple|PowerPC.*|SVA|eh-experimental|ggreif|non-call-eh|parallel|release_.*|vector_llvm|wendling|May2007|checker|cremebrulee|start|RELEASE_1.*|RELEASE_2[0-7])" Several problems here: 1. Bunch of additional branches / tags are created due to multiple branch points. I don't recall for llvm, but for clang we'll end with two tags per each release. Something like: $ git branch -r trunk tags/RELEASE_26 tags/RELEASE_26 at 84...

Hi, I've a short question: Does there exist any llvm pass that transforms an irreducible CFG into a reducible one? So far i didn't find any implementation on the internet, only an old feature request from 2003: https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_1/docs/OpenProjects.html (under "Miscellaneous Improvements") It would be exactly the thing that i need. Best Regards Moritz -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100319/8832f900/attachm...

...e control system for all the >> llvm projects is svn, I'd just as soon use svn as the tool at my end. > The git mirrors only contain what's in trunk in the SVN repos. I think it contains branches of several previous releases: $ git branch -r llvm-upstream/master llvm-upstream/release_1 llvm-upstream/release_16 llvm-upstream/release_20 llvm-upstream/release_21 llvm-upstream/release_22 llvm-upstream/release_23 llvm-upstream/release_24 llvm-upstream/release_25 llvm-upstream/release_26 llvm-upstream/release_27 llvm-upstream/release_28 llvm-upstream/release_29...

...rectory. > Surely not (at the server) > >> git svn init --stdlayout https://<user>@llvm.org/svn/llvm-project/llvm \ >> --ignore-paths="^.*(Apple|PowerPC.*|SVA|eh-experimental|ggreif|non-call-eh|parallel|release_.*|vector_llvm|wendling|May2007|checker|cremebrulee|start|RELEASE_1.*|RELEASE_2[0-7])" > Several problems here: > 1. Bunch of additional branches / tags are created due to multiple > branch points. I don't recall for llvm, but for clang we'll end with > two tags per each release. Something like: > $ git branch -r > trunk > ta...