1) Last I saw, tortoisegit was barely functional. I doubt it's anywhere
near production quality yet. You really should try git-gui and gitk, they
are quite functional. Sure they're a bit ugly, but they work well. Git
isn't svn, and some of the biggest differences (the index, only staging part
of a file to commit) really don't lend themselves to working in explorer.
There is another project out there called git extensions that's somewhere
in the middle between tortoise and git-gui. It was functional last I tried
it.
In short, don't be stubborn here, you're willing to try git, you should be
willing to try the GUI tools that come with it. If you can look past the
"ugly" you might find they're really not that bad.
2) Our registration process is one step. Enter a username, password
(twice) and email. Because it's so simple, we're not exactly sold on the
whole idea of OpenID with our site. As such, we don't currently have any
plans to add OpenID support.
Tekkub
GitHub Tech Support
http://support.github.com/
Join us on IRC: #github on freenode.net
Discussion group: [email protected]
On Thu, Apr 30, 2009 at 6:44 PM, Nazgulled <[email protected]> wrote:
>
> Hi,
>
> I've always used SVN and TortoiseSVN as I mostly develop for Windows
> and that's not going to change any time soon...
>
> Overall, I like the concept of Git and the whole GitHub website, it
> also looks much better than Google Code. But there's a few things
> that's keeping me from GitHub...
>
> 1) Is TortoiseGit good enough to be used in production systems? A
> friend of mine didn't inspired me much about using TortoiseGit (not
> Git itself), but without a TortoiseSVN alike for Git, I don't have any
> intentions of using GitHub or any other Git based revision control
> system for that matter. The opinions on this group may be a little
> biased, but I still want to hear them...
>
> 2) Now days, most people as a Google Account but not a GitHub account
> and that will not change. Google provides a lot of different
> services... The problem with this for me is that I also wanted to use
> GitHub to control issues with my applications, using your integrated
> issue system. But people need to be registered for that...
>
> Are there any possibilities to have people posting issues without
> signing up on Git? They might not be developers at all and just post
> some issues about my software... Maybe not all features can possibly
> be enable, but create issues and comment on that, would be nice to
> have without signing up. And maybe make it an option per repository...
> Another and probably better idea, would be to implement OpenID on
> GitHub, this way, every one with a Google Account (and many other
> providers) would be able to use the website. Maybe you could limit
> what this OpenID account type could on the site...
>
> Wat do you think?
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"GitHub" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/github?hl=en
-~----------~----~----~----~------~----~------~--~---
