Junio C Hamano wrote:
> Jonathan Nieder writes:
>> 1. Using multiple versions of Git on a single machine. For example,
>> some IDEs bundle a particular version of Git, which can be a
>> different version from the system copy, or on a Mac, /usr/bin/git
>> quickly goes out of sync
Jonathan Nieder writes:
> 1. Using multiple versions of Git on a single machine. For example,
> some IDEs bundle a particular version of Git, which can be a
> different version from the system copy, or on a Mac, /usr/bin/git
> quickly goes out of sync with the Homebrew git in
>
Hi,
Ben Peart wrote:
> While I can understand the user confusion the warning about ignoring an
> extension could cause I guess I'm a little surprised that people would see
> it that often. To see the warning means they are running a new version of
> git in the same repo as they are running an
On 11/12/2018 8:05 PM, Junio C Hamano wrote:
Jonathan Nieder writes:
Since 3b1d9e04 (eoie: add End of Index Entry (EOIE) extension,
2018-10-10) Git defaults to writing the new EOIE section when writing
out an index file. Usually that is a good thing because it improves
threaded
Jonathan Nieder writes:
> Since 3b1d9e04 (eoie: add End of Index Entry (EOIE) extension,
> 2018-10-10) Git defaults to writing the new EOIE section when writing
> out an index file. Usually that is a good thing because it improves
> threaded performance, but when a Git repository is shared with
Since 3b1d9e04 (eoie: add End of Index Entry (EOIE) extension,
2018-10-10) Git defaults to writing the new EOIE section when writing
out an index file. Usually that is a good thing because it improves
threaded performance, but when a Git repository is shared with older
versions of Git, it
6 matches
Mail list logo
