May 18, 2012
On Windows, I use msysgit
http://code.google.com/p/msysgit/

Somehow it's slower than the Linux counterpart, but I guess it works pretty well.

On 5/18/2012 2:58 PM, Lars T. Kyllingstad wrote:
> I remember back when we were considering whether to move DMD, Phobos and druntime from SVN on DSource to Git on GitHub, there were some concerns about using Git on Windows.  People claimed that Git was a very Linux-centric tool, and that Windows support was buggy at best.
> 
> Still, we made the switch, and I haven't really registered that many complaints since.  So now I'm curious:  Windows users, have you just resigned, or did Git actually turn out to work well on Windows? Specifically, is it usable from the CMD command line, and are graphical front-ends such as TortoiseGit any good?  (I know running it through Cygwin works well, but that doesn't count.)
> 
> -Lars

May 18, 2012
18.05.2012 11:58, Lars T. Kyllingstad написал:
> I remember back when we were considering whether to move DMD, Phobos and
> druntime from SVN on DSource to Git on GitHub, there were some concerns
> about using Git on Windows. People claimed that Git was a very
> Linux-centric tool, and that Windows support was buggy at best.
>
> Still, we made the switch, and I haven't really registered that many
> complaints since. So now I'm curious: Windows users, have you just
> resigned, or did Git actually turn out to work well on Windows?
> Specifically, is it usable from the CMD command line, and are graphical
> front-ends such as TortoiseGit any good? (I know running it through
> Cygwin works well, but that doesn't count.)
>
> -Lars

I'm happy with TortoiseGit (there was a few crashes recently but it isn't annoying) and TortoiseHg. IMHO, they are as easy as GitHub's Fork->Edit->Pull GUI.

-- 
Денис В. Шеломовский
Denis V. Shelomovskij
May 18, 2012
On 18-05-2012 10:02, Mehrdad wrote:
> I couldn't git it working at first, but it wasn't too bad when it
> finally worked. :P
>
>
> Mainly, what you need is for someone to spend 15 minutes and explain to
> you how the push/pull/commit/etc. model works, how many
> stores/repositories are there and why, etc... when a friend of mine did
> that, it was easy enough to understand (though doing it with git-bash is
> still annoying).

Personally, I've always preferred the CLI over ~most GUIs. `git gui` is fairly useful for pre-commit review and staging, etc.

But to each their own!

-- 
Alex Rønne Petersen
alex@lycus.org
http://lycus.org
May 18, 2012
On 18-05-2012 12:07, Manu wrote:
> On 18 May 2012 11:38, Ary Manzana <ary@esperanto.org.ar
> <mailto:ary@esperanto.org.ar>> wrote:
>
>     Are you happy with Windows? :-P
>
>
> Completely.

Monster.

*runs* ;-P

-- 
Alex Rønne Petersen
alex@lycus.org
http://lycus.org
May 18, 2012
On 18-05-2012 10:58, Joseph Rushton Wakeling wrote:
> On 18/05/12 09:58, Lars T. Kyllingstad wrote:
>> Still, we made the switch, and I haven't really registered that many
>> complaints
>> since. So now I'm curious: Windows users, have you just resigned, or
>> did Git
>> actually turn out to work well on Windows?
>
> I'm mostly a Linux-user, but I have played with Git on Windows and don't
> recall it being particularly different from the Linux experience. I'd
> have thought the main issue would be that Windows-oriented people aren't
> used to using command-line stuff (in my experience this can extend to
> devs as well as regular users).

I think that's the primary issue - Windows devs expect a full-blown, well-developed, and concise GUI. Git, frankly, doesn't have one. And I think that using a GUI for Git doesn't make an awful lot of sense; controlling the branching model, submodules, remotes, the stash, rebasing, etc is pretty hard from a GUI compared to the CLI (in my own not so humble opinion).

I like to think that GUIs and CLIs both have their uses. I use the CLI to do most Git work, but *strongly* prefer `git gui` to do pre-commit review, staging, reverting, etc.

-- 
Alex Rønne Petersen
alex@lycus.org
http://lycus.org
May 18, 2012
On 18-05-2012 11:07, Norbert Nemec wrote:
> In my experience, TortoiseGIT is rather awkward to use. Anyone looking
> for a GUI for git should have a look at SmartGIT. It is commercial but
> zero cost for non-commercial use, available for Win/Mac/Linux and I
> don't know any other GUI that comes even close in quality.

I hadn't even heard of that one until reading this thread. Will definitely have a look at that.

>
> I guess there will always be some expert operations that require using
> the git CLI. This is just as usable on Windows as it is on Unix, but
> Windows users tend to avoid CLI in general. Anyhow, a user who migrates
> from SVN to GIT would not even miss that kind of operations.

Unfortunately, they'd be missing out on all the cool Git features then. ;)

>
> In general I don't see any aspect where GIT is less adapted to Windows
> than any other version control.
>
>
>
> On 18.05.2012 09:58, Lars T. Kyllingstad wrote:
>> I remember back when we were considering whether to move DMD, Phobos and
>> druntime from SVN on DSource to Git on GitHub, there were some concerns
>> about using Git on Windows. People claimed that Git was a very
>> Linux-centric tool, and that Windows support was buggy at best.
>>
>> Still, we made the switch, and I haven't really registered that many
>> complaints since. So now I'm curious: Windows users, have you just
>> resigned, or did Git actually turn out to work well on Windows?
>> Specifically, is it usable from the CMD command line, and are graphical
>> front-ends such as TortoiseGit any good? (I know running it through
>> Cygwin works well, but that doesn't count.)
>>
>> -Lars
>


-- 
Alex Rønne Petersen
alex@lycus.org
http://lycus.org
May 18, 2012
On Friday, 18 May 2012 at 07:58:26 UTC, Lars T. Kyllingstad wrote:
> I remember back when we were considering whether to move DMD, Phobos and druntime from SVN on DSource to Git on GitHub, there were some concerns about using Git on Windows.  People claimed that Git was a very Linux-centric tool, and that Windows support was buggy at best.
>
> Still, we made the switch, and I haven't really registered that many complaints since.  So now I'm curious:  Windows users, have you just resigned, or did Git actually turn out to work well on Windows?  Specifically, is it usable from the CMD command line, and are graphical front-ends such as TortoiseGit any good?  (I know running it through Cygwin works well, but that doesn't count.)
>
> -Lars

I'm using both, Linux and Windows, but I prefer working on Windows (I don't have X on my Linux installation, and it's not very cozy to spend all day in console). On Windows I have MSYS + Console2 setup, so I basically have nice looking (and more importantly functional) Linux console on my Windows.

Oh, and yes, git (msysgit actually) is working great on Windows (just a bit slower than Linux version, but still faster than svn).
May 18, 2012
So far I like git-cola the most of all the git front ends I have tried. It takes a little bit of work but it can be made to run on windows


May 18, 2012
On 18-05-2012 09:58, Lars T. Kyllingstad wrote:
> I remember back when we were considering whether to move DMD, Phobos and
> druntime from SVN on DSource to Git on GitHub, there were some concerns
> about using Git on Windows. People claimed that Git was a very
> Linux-centric tool, and that Windows support was buggy at best.

Linux-centric - yes. Buggy - no. msysgit (which is really what all Git packages on Windows are based on) has evolved a lot and is very high quality. I've used it on ~20 projects total by now, with all sorts of crazy hacks (git rerere, git rebase, git filter-branch) and it Just Works.

>
> Still, we made the switch, and I haven't really registered that many
> complaints since. So now I'm curious: Windows users, have you just
> resigned, or did Git actually turn out to work well on Windows?
> Specifically, is it usable from the CMD command line, and are graphical
> front-ends such as TortoiseGit any good? (I know running it through
> Cygwin works well, but that doesn't count.)
>
> -Lars

Git kinda-sorta works in cmd.exe, but I really wouldn't recommend it. Not only because cmd.exe just plain *sucks*, but also because it lacks a lot of features that tools designed for UNIX (such as Git) use. mintty is a great replacement.

I'm not a full-time Windows user, but when I do work on Windows, Git Bash and mintty work great for Git (note that Git Bash is really just bash.exe running inside cmd.exe).

BTW, running Git through Cygwin isn't all that much different from running it in Git Bash (msysgit). Both of those use cmd.exe as the 'shell'. As I mentioned above, I would really recommend using mintty.

I would not recommend TortoiseGit, or Tortoise* in general. In my personal experience, they've been very good at screwing up repos because what I thought some action would do didn't match the command line term for the operation. It's great that GUIs try to make things intuitive, but it can certainly backfire on people who are used to the CLI.

-- 
Alex Rønne Petersen
alex@lycus.org
http://lycus.org
May 18, 2012
On 18 May 2012 15:41, Alex Rønne Petersen <alex@lycus.org> wrote:

> On 18-05-2012 12:07, Manu wrote:
>
>> On 18 May 2012 11:38, Ary Manzana <ary@esperanto.org.ar <mailto:ary@esperanto.org.ar>> wrote:
>>
>>    Are you happy with Windows? :-P
>>
>>
>> Completely.
>>
>
> Monster.
>
> *runs* ;-P


Well it's hard to escape the zombie apocalypse: http://www.netmarketshare.com/chartfx62/temp/CFT0518_09091906FE0.png (recent google statistics)


1 2 3 4 5 6
Top | Discussion index | About this forum | D home