git-for-windows/git
1
0
Fork 0
mirror of https://github.com/git-for-windows/git.git synced 2025-12-11 19:22:58 -06:00
Code Issues Packages Projects Releases 335 Wiki Activity

Use the new homepage consistently 

We now use the domain gitforwindows.org, which is much easier to
remember and quicker to type.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Johannes Schindelin 2018-02-12 11:08:44 +01:00
parent 4f5edb5d56
commit 9786dc0b7f
11 changed files with 24 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Building-Git.md

@ -1,14 +1,14 @@
We build Git for Windows using an [MSYS2](https://msys2.github.io/) based *Git for Windows SDK*. This SDK can be installed via the [SDK installer](https://git-for-windows.github.io/#download-sdk)
We build Git for Windows using an [MSYS2](https://msys2.github.io/) based *Git for Windows SDK*. This SDK can be installed via the [SDK installer](https://gitforwindows.org/#download-sdk)
# Installing a build environment
1. Just run the [SDK installer](https://git-for-windows.github.io/#download-sdk).
1. Just run the [SDK installer](https://gitforwindows.org/#download-sdk).
# Build Git
1. An initial `git clone` and `make` should have already occurred when running the [SDK installer](https://git-for-windows.github.io/#download-sdk).
1. An initial `git clone` and `make` should have already occurred when running the [SDK installer](https://gitforwindows.org/#download-sdk).
2. Open the *Git for Windows SDK* *MinGW* shell by double clicking either the Shortcut on the desktop `Git SDK 32-bit.lnk` or by double clicking `mingw32_shell.bat` in the install folder. That is `Git SDK 64-bit.lnk` and `mingw64_shell.bat` for the `64bit` [SDK installer](https://git-for-windows.github.io/#download-sdk).
2. Open the *Git for Windows SDK* *MinGW* shell by double clicking either the Shortcut on the desktop `Git SDK 32-bit.lnk` or by double clicking `mingw32_shell.bat` in the install folder. That is `Git SDK 64-bit.lnk` and `mingw64_shell.bat` for the `64bit` [SDK installer](https://gitforwindows.org/#download-sdk).
2. Change directory to the initial clone: `cd /usr/src/git`.

2
Building-msys2-runtime.md

@ -1,6 +1,6 @@
# Installing a build environment
1. Just run the [SDK installer](https://git-for-windows.github.io/#download-sdk).
1. Just run the [SDK installer](https://gitforwindows.org/#download-sdk).
# Build `msys2-runtime`

2
Debugging-Git.md

@ -2,7 +2,7 @@
First of all, Git's `.exe` files should be rebuilt with debugging information, and without optimization (because `gdb` has serious troubles single-stepping code compiled using `-O2` for some reason). To this end:
1. [install the Git for Windows SDK](https://git-for-windows.github.io/#download-sdk)
1. [install the Git for Windows SDK](https://gitforwindows.org/#download-sdk)
2. edit `/usr/src/git/Makefile` to remove the `-O2` from the `CFLAGS = -g -O2 -Wall` line,
3. run `make` in `/usr/src/git/`.

4
FAQ.md

@ -8,7 +8,7 @@ NOTE: Git for Windows version [2.10.0](https://github.com/git-for-windows/git/re
Windows XP and Windows Server 2003 are long past their end of life, hence support for these versions was dropped from Git for Windows 2.10.1 and later. This limitation is inherited by Git's use of MSYS2, which in turn inherited it from [Cygwin](https://cygwin.com/ml/cygwin/2015-08/msg00446.html).
More information here: [Git for Windows' prerequisites](https://git-for-windows.github.io/requirements.html).
More information here: [Git for Windows' prerequisites](https://gitforwindows.org/requirements.html).
## Is there an MSI for installation via Group Policy?
@ -92,4 +92,4 @@ Git is an Open Source project covered by the GNU General Public License version
Git for Windows also contains Embedded CAcert Root Certificates. For more information please go to https://www.cacert.org/policy/RootDistributionLicense.php.
This package contains software from a number of other projects including Bash, zlib, curl, tcl/tk, perl, MSYS2 and a number of libraries and utilities from the GNU project, licensed under the GNU General Public License. Likewise, it contains Perl which is dual licensed under the GNU General Public License and the Artistic License.
This package contains software from a number of other projects including Bash, zlib, curl, tcl/tk, perl, MSYS2 and a number of libraries and utilities from the GNU project, licensed under the GNU General Public License. Likewise, it contains Perl which is dual licensed under the GNU General Public License and the Artistic License.

2
Home.md

@ -1,5 +1,5 @@
# Introduction
The _Git for Windows_ wiki. It looks more technical than [our home page](https://git-for-windows.github.io/) because it is the place where *you* [can contribute](https://github.com/git-for-windows/git/wiki/How-to-participate) to the documentation about _Git for Windows_.
The _Git for Windows_ wiki. It looks more technical than [our home page](https://gitforwindows.org/) because it is the place where *you* [can contribute](https://github.com/git-for-windows/git/wiki/How-to-participate) to the documentation about _Git for Windows_.
## About
_Git for Windows_ is very different from _Git_ for almost everything else in one important respect: Windows does not provide the *POSIX* infrastructure Git expects.

6
How-to-participate.md

@ -1,4 +1,4 @@
There are several ways to participate in the Git for Windows project. First off, have a look at the [governance model](http://git-for-windows.github.io/governance-model.html) of the project.
There are several ways to participate in the Git for Windows project. First off, have a look at the [governance model](https://gitforwindows.org/governance-model.html) of the project.
# Help users
@ -10,10 +10,10 @@ A lot of documentation wants to be written, still. A good place is [the Git for
# Fix bugs or add features in the Git code itself
Download [the SDK](http://git-for-windows.github.io/#download-sdk) and build Git. Also have a look at [this page](https://github.com/git-for-windows/git/wiki/Building-Git) for tips and tricks revolving around building and debugging Git.
Download [the SDK](https://gitforwindows.org/#download-sdk) and build Git. Also have a look at [this page](https://github.com/git-for-windows/git/wiki/Building-Git) for tips and tricks revolving around building and debugging Git.
Please also sign off your work, as [asked by the Git project](https://github.com/git/git/blob/v2.3.5/Documentation/SubmittingPatches#L234-L286)
After that, submit a Pull Request.
Sometimes there are good suggestions how to improve the patches in a Pull Request. When that happens, just [rewrite and force-push the branch](https://robots.thoughtbot.com/git-interactive-rebase-squash-amend-rewriting-history).
Sometimes there are good suggestions how to improve the patches in a Pull Request. When that happens, just [rewrite and force-push the branch](https://robots.thoughtbot.com/git-interactive-rebase-squash-amend-rewriting-history).

4
Making-a-portable-Git.md

@ -1,6 +1,6 @@
As the portable Git is made by putting together files from the Git SDK, it is advisable to update those files first. To update the packages, call `pacman -Syu` ([caveats apply](https://github.com/git-for-windows/git/wiki/Package-management#updating-msys2-runtime-pacman-and-bash)). If you want to test Git changes or make an portable Git from your own Git fork, you need to call `cd /usr/src/git && make install` (for documentation changes, `make install-html` and *afterwards* `prefix=/mingw64 make -C contrib/subtree install-html` - without the second `make` you get a error message about a missing `git-subtree.html` file).
To package the portable Git, install the [SDK](https://git-for-windows.github.io/#download-sdk), run it and then issue the following commands:
To package the portable Git, install the [SDK](https://gitforwindows.org/#download-sdk), run it and then issue the following commands:
```bash
cd /usr/src/build-extra
@ -9,4 +9,4 @@ git checkout master
./portable/release.sh <version>-test
```
where `<version>` is the Git version.
where `<version>` is the Git version.

4
Making-an-installer.md

@ -20,7 +20,7 @@ prefix=/mingw64 make -C contrib/subtree install-html
>without this second `make` you get an error message about a missing `git-subtree.html` file).
To make an installer, install the [SDK](https://git-for-windows.github.io/#download-sdk) and run it
To make an installer, install the [SDK](https://gitforwindows.org/#download-sdk) and run it
>Git for Windows SDK MinGW shell can be run by double-clicking either the Shortcut on the desktop Git SDK 32-bit.lnk or by double-clicking mingw32_shell.bat in the install folder. That is Git SDK 64-bit.lnk and mingw64_shell.bat for the 64bit SDK installer.
@ -32,4 +32,4 @@ git pull master
./installer/release.sh <version>-test
```
where `<version>` is the Git version (please note that the `<version>` cannot contain dots after the numerical version: `2.7.2-hello-world` is okay while `2.7.2.hello.world` is not okay).
where `<version>` is the Git version (please note that the `<version>` cannot contain dots after the numerical version: `2.7.2-hello-world` is okay while `2.7.2.hello.world` is not okay).

4
Rebasing-Git-for-Windows.md

@ -5,7 +5,7 @@ To do a *rebase* of the *Git for Windows* source onto a new [upstream](https://g
2. The latest *rebase* was done onto a [upstream](https://github.com/git/git) release tagged as `v2.3.3`
# Preconditions
1. A working [Git for Windows SDK](https://git-for-windows.github.io/#download-sdk).
1. A working [Git for Windows SDK](https://gitforwindows.org/#download-sdk).
2. A fetched build-extra repository.
`cd /usr/src/build-extra`
`git fetch`
@ -37,4 +37,4 @@ To do a *rebase* of the *Git for Windows* source onto a new [upstream](https://g
>It's a bit hard to read, though, because it is a diff of a diff.
>So meta.
>When there is a line that starts with a `-` or a `+` but then continues with a space, that's good!
>It means that the context of our changes changed.
>It means that the context of our changes changed.

4
Technical-overview.md

@ -6,7 +6,7 @@ The process to build installer is made easy via the `Git for Windows SDK`. The s
# Installing the SDK
Download the [SDK](https://git-for-windows.github.io/#download-sdk) and run it. You will end up with a console window running the `Git for Windows SDK` shell, which you can use for the next steps. Git is already checked out and the latest version build and installed, so if you just want to build an installer from latest master, you are ready to go.
Download the [SDK](https://gitforwindows.org/#download-sdk) and run it. You will end up with a console window running the `Git for Windows SDK` shell, which you can use for the next steps. Git is already checked out and the latest version build and installed, so if you just want to build an installer from latest master, you are ready to go.
You can open the `Git for Windows SDK` shell by double clicking `git-bash.exe` in the install folder.
@ -58,4 +58,4 @@ See also:
* [Debugging git](Debugging-Git) with gdb
* Running Git's [regression tests](Running-Git's-regression-tests)
* Msys/Mingw [package management](Package-management#technical-details)
* [Updating the SDK](https://github.com/git-for-windows/git/wiki/Updating-your-SDK)
* [Updating the SDK](https://github.com/git-for-windows/git/wiki/Updating-your-SDK)

8
Vagrant.md

@ -1,6 +1,6 @@
# Introduction
[Vagrant](https://www.vagrantup.com/) is a modern way to define the requirements of a project. In the case of [Git for Windows](http://git-for-windows.github.io/), it allows us to set up a minimal virtual Linux machine that makes it easy to run the same revision of Git on Windows as well as on Linux without much effort.
[Vagrant](https://www.vagrantup.com/) is a modern way to define the requirements of a project. In the case of [Git for Windows](https://gitforwindows.org/), it allows us to set up a minimal virtual Linux machine that makes it easy to run the same revision of Git on Windows as well as on Linux without much effort.
**Note**: while Vagrant makes things easy, quite a bit of bandwidth is required for the setup (roughly a gigabyte will be downloaded in total).
@ -8,7 +8,7 @@
1. Download and install [VirtualBox](https://www.virtualbox.org)
2. Download and install [Vagrant](https://www.vagrantup.com/)
3. Install the [Git SDK](http://git-for-windows.github.io/#download-sdk)
3. Install the [Git SDK](https://gitforwindows.org/#download-sdk)
4. Run `vagrant up` in the `/usr/src/git` directory
5. Run `vagrant ssh`
@ -18,7 +18,7 @@ To compile and install Git, you will have to run `make clean` first because *Git
# Alternative to the Git SDK way
If you cannot download and install the Git SDK for some reason or other, you could also clone [the Git source code](https://github.com/git-for-windows/git) using [Git for Windows](https://git-for-windows.github.io/) instead, but make sure that Unix line endings are used: `git clone -c core.autocrlf=false https://github.com/git-for-windows/git vagrant-git`. If Git for Windows does not even work for you, you could also download the source code [as a `.zip`](https://github.com/git-for-windows/git/archive/master.zip) and unpack it.
If you cannot download and install the Git SDK for some reason or other, you could also clone [the Git source code](https://github.com/git-for-windows/git) using [Git for Windows](https://gitforwindows.org/) instead, but make sure that Unix line endings are used: `git clone -c core.autocrlf=false https://github.com/git-for-windows/git vagrant-git`. If Git for Windows does not even work for you, you could also download the source code [as a `.zip`](https://github.com/git-for-windows/git/archive/master.zip) and unpack it.
After that, continue with the `vagrant up` step above.
@ -52,4 +52,4 @@ sudo mount -t tmpfs -o size=10G tmpfs $HOME/tmp
cd $HOME/tmp
```
You will want to clone projects into that `$HOME/tmp/` directory so that the I/O intensive operations benefit fully from using Vagrant.
You will want to clone projects into that `$HOME/tmp/` directory so that the I/O intensive operations benefit fully from using Vagrant.