search for: tortoisegit

...t linaro.org> wrote: > I think we should start two other threads: one about git tooling on Windows > and one about infrastructure problems migrating to git. Some developers on Windows prefer to use GUI tools like TortoiseSVN to command line tools for version control. The last time I tried TortoiseGit on Windows (which was over a year ago), it did not feel ready for production use on a complex project to me (I had crashes on simple operations, and it seems I was not alone in seeing flaky behavior: https://gitlab.com/tortoisegit/tortoisegit/issues/1738 and https://gitlab.com/tortoisegit/tortoiseg...

...in at linaro.org> wrote: I think we should start two other threads: one about git tooling on Windows and one about infrastructure problems migrating to git. Some developers on Windows prefer to use GUI tools like TortoiseSVN to command line tools for version control. The last time I tried TortoiseGit on Windows (which was over a year ago), it did not feel ready for production use on a complex project to me (I had crashes on simple operations, and it seems I was not alone in seeing flaky behavior: https://gitlab.com/tortoisegit/tortoisegit/issues/1738 and https://gitlab.com/tortoisegit/torto...

...wo other threads: one about git tooling on Windows > > and one about infrastructure problems migrating to git. > > Some developers on Windows prefer to use GUI tools like TortoiseSVN to > > command line tools for version control. The last time I tried > > TortoiseGit on Windows (which was over a year ago), it did not feel > > ready for production use on a complex project to me (I had crashes on > > simple operations, and it seems I was not alone in seeing flaky > > behavior:https://gitlab.com/tortoisegit/tortoisegit/issues/1738 an...

...>> I think we should start two other threads: one about git tooling on Windows >> and one about infrastructure problems migrating to git. > >Some developers on Windows prefer to use GUI tools like TortoiseSVN to >command line tools for version control. The last time I tried >TortoiseGit on Windows (which was over a year ago), it did not feel >ready for production use on a complex project to me (I had crashes on >simple operations, and it seems I was not alone in seeing flaky >behavior: https://gitlab.com/tortoisegit/tortoisegit/issues/1738 and >https://gitlab.com/torto...

IMO, if we're switching to git, we should just be clear up front that all committers will be expected to switch to git as well -- or at least, if they want to use something else (e.g. mercurial's git bridge/etc), that it's their own problem. It is truly NOT that big an imposition to require the use of git. And knowing how to use git at at least a basic level is an important skill for

On 6/3/2016 9:31 AM, David Chisnall via llvm-dev wrote: > On 3 Jun 2016, at 15:01, Aaron Ballman via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> The end result is "go use the console". Whether that's because people >> recommend it or because it's the only option is immaterial. The fact >> remains, we don't have to do that today, we may have to

On Sun, May 13, 2018 at 8:48 PM Bruce Hoult via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I recommend using https://github.com/llvm-project/llvm-project-20170507 if you can spare 1.1 GB of disk and bandwidth for the initial checkout and git repo itself. > It's just a few minutes behind the svn master copies. I don't know of a better monorepo at present. > Although