On Tue, May 31, 2016 at 02:43:02PM -0700, Matthias Braun wrote: > > > On May 31, 2016, at 2:05 PM, Joerg Sonnenberger via llvm-dev > > <llvm-...@lists.llvm.org> wrote: > > > > On Tue, May 31, 2016 at 01:45:30PM -0700, Matthias Braun wrote: > >> To be more exact here: I usually do not checkout llvm svn at a higher > >> level because that forces me back to svn (which last time I used it did > >> not have built-in support for bisection, not sure if that changed > >> recently). > > > > svn-bisect is a trival tool and should be part of every good svn > > installation. While I never got around to script the part of "update all > > subrepos to the same revision", it certainly doesn't involve any > > addition checks. From what I can tell, git submodules don't even support > > that easily. I might be wrong though. > > In a nutshell: > git-submodules basically records a git revision of your submodules with the > commits. > You can make such revision switches a natural part of commits. > "git submodule update [--recursive]" will bring your submodule checkouts in > sync with what the toplevel repository expects. > > In any way we can have this discussion separate from the discussion of moving > to git. We can stay with our current ways of matching same date for now.
But the move to git introduces the UI regression in first place. No date matching and the like is necessary with subversion. Joerg _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
