[llvm-dev] Switching to git (Windows experience) (was re:[cfe-dev] GitHub anyone?)

Craig, Ben via llvm-dev
2016-06-02T14:00:36Z

The GitHub app is ok.  Not great, but ok.  I guess this is one point in
favor of GitHub vs. other git providers.  As a maintainer on a different
project, I still had to jump out to the command line pretty frequently,
as we had a squashed pull-request work flow.

I did not have much success with git plugins for Visual Studio. They
seemed to be tuned towards in-tree builds.  I didn't spend enough time
to figure out how to get them to work with out-of-tree builds.  More
specifically, I recall that Visual Studio really expected the project
and solution to be in source control, and in the same directory
hierarchy as the source.  It's been a year since I've messed with them
though, so things might have gotten better.

On 6/2/2016 7:43 AM, Aaron Ballman via llvm-dev wrote:
> On Wed, Jun 1, 2016 at 6:31 PM, Renato Golin <renato.golin 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/tortoisegit/issues/2494 as examples).
>
> Are there suitable GUI tools for git on Windows for projects as
> complex as LLVM? I believe MSVC has some integration, but I've not
> used it before. Perhaps other tools exist that match the integration
> and stability that TortoiseSVN has with Explorer?
>
> I bring this up as a possible minor concern because asking people to
> switch from one set of command line commands to another set of command
> line commands is a different beast than asking people to switch from
> Explorer-integrated menus and dialogs to the command line (that's a
> drastically different workflow to achieve the same end result of
> source code version control).
>
> ~Aaron
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160602/6675f6f2/attachment.html>