[PATCH] D24167: Moving to GitHub - Unified Proposal

Duncan P. N. Exon Smith via llvm-commits llvm-commits at lists.llvm.org
Tue Oct 4 14:47:32 PDT 2016


> On 2016-Sep-30, at 14:30, Chris Bieneman via llvm-commits <llvm-commits at lists.llvm.org> wrote:
> 
>> 
>> GitHubMove.rst:334
>> +compiler-rt for instance. In this way it's not different from someone who would
>> +check out all the projects with SVN today.
>> +
> 
> You've lost me here. Checking out all the projects in SVN today involves multiple svn co commands. Unless there is some magic in SVN I'm unaware of. If there is such magic we should document it somewhere on LLVM.org (maybe on the getting started page?) and link to it here.

Are you thinking of "sparse checkouts", which IIRC were added in SVN 4.0?  I probably don't have the spelling right (I've barely touched SVN in years), but it's something like:
--
$ svn co --depth=empty https://llvm.org/svn/llvm-project
$ svn update --set-depth=empty    llvm-project/{llvm,cfe}
$ svn update --set-depth=infinity llvm-project/{llvm,cfe}/trunk
--
This gives you a single checkout both LLVM and CFE (obviously this scales to more sub-projects).  You could add symlinks or whatever to match your workflow and create single commits for multi-project changes.

But I'm not sure we need to document this.  Setting up the symlinks appropriately is somewhat workflow-specific, and this isn't a "getting started" hurdle; more, "advanced SVN usage".  And, realistically, most people are going to use the git-mirrors (where simultaneous commits aren't so trivial (although I heard that chapuni and jlebar might each have git-scripts for this?)).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20161004/43c27230/attachment.html>


More information about the llvm-commits mailing list