similar to: [LLVMdev] GIT mirrors

Is this going to rewrite the entire history of everything on trunk? If I have a local git repo that has been pulling from the existing mirror, what will be the implications of your change? On Mar 10, 2011, at 8:04 AM, Anton Korobeynikov wrote: > Hello Everyone > > I'm going to rebuild GIT mirrors to provide more consistent tags / branches. > Basically, the contents will be the

On Mar 10, 2011, at 9:28 AM, Bob Wilson wrote: > Is this going to rewrite the entire history of everything on trunk? If I have a local git repo that has been pulling from the existing mirror, what will be the implications of your change? The extra branches that Anton added to clang.git didn't rewrite anything. Here's hoping it won't be necessary for llvm.git either. /jakob

> The extra branches that Anton added to clang.git didn't rewrite anything. > Here's hoping it won't be necessary for llvm.git either. I was hoping that the rebuilt won't change the sha's and noone will notice anything (well, except those who already branched out of branches / tags). But it seems that after rebuild stuff was changed (I really dunno, why). So, we'll go

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

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

Anton, please add release_32 also in; clang-tools-extra compiler-rt dragonegg libcxxabi lldb They have release_32 in svn. I don't know they might be released, though. And, could you suppress generating refs/heads/svn-tags and prune them for now? I am sure that orphan branches will stress the llvm.org server to begin git-pack-ing whole tree. ...Takumi 2012/11/15 Anton Korobeynikov

> Just to be clear: we _really_ do not want all the sha's to change for trunk. Yes. That's why I said there will be other way :) In any case - please try clang.git once again. It should contain new branch/tag layout. If there will be some problems - let me know and I'll revert to prev. repository. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics,

On 2017-12-30 21:27, Anton Korobeynikov via llvm-dev wrote: > Hello > > We are not planning to use git tags there (at least until the git > migration would happen). Please use the release branches. To me it doesn't matter if it's a tag or a branch, but, as far as I can see, there are no branches for point releases. For example, there's a branch release_50, but no branch

Should be there On Fri, Nov 16, 2012 at 3:00 PM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > Anton, please add release_32 also in; > > clang-tools-extra > compiler-rt > dragonegg > libcxxabi > lldb > > They have release_32 in svn. I don't know they might be released, though. > > And, could you suppress generating refs/heads/svn-tags and prune them

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

On Mar 10, 2011, at 10:39 AM, Anton Korobeynikov wrote: >> The extra branches that Anton added to clang.git didn't rewrite anything. >> Here's hoping it won't be necessary for llvm.git either. > I was hoping that the rebuilt won't change the sha's and noone will > notice anything (well, except those who already branched out of > branches / tags). > But

> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. Unfortunately, this requires manual grafting, since git-svn does really bad job here. I'm going to work on this tonight. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Should be there. Please let me know if there are any problems with them On Wed, Nov 14, 2012 at 9:19 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. > Unfortunately, this requires manual grafting, since git-svn does > really bad job here. > > I'm going

Thanks, Anton. I always forget about llvm-admin :). I'd say converting all branches would be best, would help track the MCJIT work for example. Gaël, does that sound good to you? You're the one making all the commits these days :). ~Will On Sun, Jan 5, 2014 at 9:03 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Hello > > I can create a mirror, this is not

Hi, Has there been discussion about having svn mirror git instead of vice versa? I've been happy with the git+cmake+ninja combo for a while now, but the online docs suggests this configuration is second-class to svn+autotools+make. Is the community transitioning to any particular configuration? Thanks, Greg On Wed, Nov 14, 2012 at 9:19 AM, Anton Korobeynikov <anton at

Yeah, it seems that the time the mirror was created there were no release branches and therefore nothing was exported :) On Fri, Nov 20, 2015 at 8:13 PM, Hans Wennborg <hans at chromium.org> wrote: > On Thu, Nov 19, 2015 at 2:38 PM, Martell Malone via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi All, >> >> I am currently trying to test out a few things

On Thu, Mar 10, 2011 at 2:53 PM, Anton Korobeynikov <anton at korobeynikov.info > wrote: > > Just to be clear: we _really_ do not want all the sha's to change for > trunk. > Yes. That's why I said there will be other way :) > > In any case - please try clang.git once again. It should contain new > branch/tag layout. If there will be some problems - let me know

I've noticed that there are no tags in any of the Git mirrors [1], [2] or [3]. Would it be possible to add the tags? [1] https://git.llvm.org/git/llvm.git [2] https://github.com/llvm-mirror/llvm [3] https://github.com/llvm-project/llvm-project-20170507 -- /Jacob Carlborg

Git tags and SVN tags are completely different beasts (git tag is simply a "second name" attached to revision, while on svn the tag could be arbitrary different). There is no way to automate the process - in general svn tag might not correspond (by contents) to any other revision in the repository. The only way to somehow emulate svn tags on git is to create a separate branch on each

This has been discussed many times. Might want to take a look in the mailing list archives. :) cmake and autotools are on roughly equal footing at this point with chandler and I handling each of them respectively and fairly quickly. git vs. svn is a different story though. -eric On Thu, Nov 15, 2012 at 8:31 AM, Greg Fitzgerald <garious at gmail.com> wrote: > Hi, > > Has there