Windows 10: Whats the right way to use Git on Windows 10?

/u/doutorchefe · Nov 13, 2020

Hello fellows. After more than 15 years on Linux I'm migrating to Windows 10 this year. Things seems to be more user friendly now. It was pretty annoying initially but I finally managed how to block Cortana, Start Menu Web Search and others craps through firewall and gpedit (I'm still having to deal with Windows Store installing what I don't asked to). But what's the right way to use Git on Windows? I'm still lost on this.

It just doesn't feel right, Git doesn't seems to like the Windows' EOL nor File System. The official Git installer seems to emulate a Linux terminal inside of Windows, it doesn't feels native. I tried to run it through WSL2 but it is extremely slow. I moved all my projects inside WSL2 file system, but this doesn't feel right either, now I have two File System to Back Up, I'm gonna need to have Duplicati or Duplicity running inside of WSL2. By the way, how do you manage your WSL2 (dot files and projects)? I don't know if Windows Users have this habit of having backups. Exporting the vhdx .tar and sending it to the cloud doesn't seems to be the right way (yep, this was suggested to me).

By the way, a tip to my friends coming from Linux to Windows, put this file on your WSL2, this will help a lot with ACL on Windows File System and its gonna mount your C:/ and D:/ on /c and /d:

#/etc/wsl.conf [automount] root = / options = "metadata,umask=022,fmask=011"

Well, still getting used to it, I hope Windows migrate to a better File System and run on top of a Linux Kernel some day . Things are getting better, I'm anxious to learn the new .NET5.0

submitted by /u/doutorchefe
[link] [comments]

:)

Brink · Nov 13, 2020

What’s new in Git for Windows 2.11?

Git for Windows v2.11.0 is out! Download it here (homepage is here).

The new version corresponds to Git v2.11.0 (release notes are here, and our friends over at GitHub blogged about it, too). Apart from the improvements inherited from the “upstream Git” project, Git for Windows also updated some libraries to address security concerns, and dropped support for Windows XP.

Performance improvements

The new Git version features speed improvements all over the place. It is my pleasure to say that some of these improvements originate in the Git for Windows project itself, such as the acceleration of git rebase‘s startup phase by making the patch ID generation smarter.

A few more speedups went into Git for Windows specifically

the hash generation now leverages OpenSSL’s Intel CPU support, which speeds it up noticeably.

When working in large worktrees, git add is now a lot faster.

The “fscache” feature that already speeds up most disk accesses now plays better with sparse checkouts.

The internal cache to handle file names in a case-insensitive manner is now much more efficient.

Even if Git for Windows does not ship with Git LFS (due to size concerns), the new Git for Windows has support for substantially faster clones when using many binary files managed by Git LFS.

Experimental, faster difftool

One of the factors contributing to Git for Windows “feeling” slower than, say, Git on Linux, is the fact that some Git functionality is actually not implemented in native code, but as shell or Perl script. As neither a shell nor a Perl are provided by default in a regular Windows setup, Git for Windows ships with a “pseudo POSIX” environment called MSYS2 (which is in turn based on Cygwin). The need for this POSIX emulation layer slows things down considerably.

That is the reason why the Git for Windows converts scripted parts into native code, as was done with the interactive rebase in Git for Windows v2.10.

In Git for Windows v2.11, there is now a difftool that is a “builtin”, i.e. native code. As the new builtin difftool needs more wide-spread testing, it is an opt-in feature; by default, git difftool will still call the original script.

Visual Studio support

By far the most effort in the v2.11 cycle has gone into building Git for Windows’ master branch with Visual Studio. In fact, there are two ways to build via Visual C: using the command-line, and in Visual Studio. Both options work using Visual Studio’s Community edition, by the way.

I would like to indulge in enumerating just a couple of the goodies now available to us:

Code navigation! The Ctrl+, keyboard shortcut to navigate to declarations, definitions, and files, is easily my most favorite tool here.

Refactoring tools! Visual Studio comes with a couple of functions that make refactoring much more painless.

Debugging! Visual Studio’s integrated debugger offers nifty features such as inspecting code, single-stepping, and hot-patching changed code. It is hard not to love having those options.

Profiling tools! These tools already helped identify a couple of bottlenecks.

It was far from easy to get to that point, and I cannot thank enough all the people involved with this effort, in particular Jeff Hostetler and Philip Oakley, for their tenacity and code contributions. Git for Windows already had a script to generate Visual Studio project definitions since 2009, with a recent effort to bring the script up-to-date and to fix Git’s source code to build correctly.

The official Git for Windows will still be built with GNU C (“GCC”), simply because you should never change a winning team. Oh, and the Git project itself uses GCC, too, hence we avoid battling unnecessary fights by sticking to GNU C for the official releases.

But it is really nice to have the option to simply clone, check out the vs/master branch, immediately start playing with the source code, and then run the test suite from a regular Git Bash (no Git for Windows SDK required).
Click to expand...

Source: Whats new in Git for Windows 2.11? | Microsoft Application Lifecycle Management

carlosmontiel1 · Nov 13, 2020

Restricting domain and public access to Git

Hi Dave,

Sorry if my question isn't a good one, I really am new to Git. I know there are two methods, Git and GitHub right? Is GitHub the only way to add these restrictions and/ or can it also be done with Git? Again, apologies in advance if my question isn't a good
one.

Ahhzz · Nov 13, 2020

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

Open a new Explorer window.

Click View in the ribbon.

Click Options.

Under General, next to “Open File Explorer to:” choose “This PC.”

Click OK

credit to Lifehacker.

Windows 10: Whats the right way to use Git on Windows 10?

Whats the right way to use Git on Windows 10?

Whats the right way to use Git on Windows 10?

Whats the right way to use Git on Windows 10?

Whats the right way to use Git on Windows 10? - Similar Threads - Whats right Git

How to Use OneDrive the Right ? Way

How to Use OneDrive the Right ? Way

How to Use OneDrive the Right ? Way

git and pywb

What's the right way to backup my laptop?

Using GIT GUI on Microsoft

git gui

What's the Right Way To Uninstall Audacity

What’s new in Git for Windows 2.11?