The latest feature release Git v1.8.2 is now available at the
usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
42960ec7c2d8404af3d3f6d21f32f1e97e6e0a96 git-1.8.2.tar.gz
db1ca968f492f7ad1d4e0c13d07f23c745d10b74
Junio C Hamano writes:
> Matthieu Moy writes:
>
>> A few suggestions on the release notes (you may safely ignore)
>
> They both look very sensible, at least to me. Perhaps like this?
Looks good, yes.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
To unsubscribe from this list: send the
Matthieu Moy writes:
> A few suggestions on the release notes (you may safely ignore)
They both look very sensible, at least to me. Perhaps like this?
Thanks.
Documentation/RelNotes/1.8.2.txt | 60 +++-
1 file changed, 34 insertions(+), 26 deletions(-)
di
A few suggestions on the release notes (you may safely ignore)
Junio C Hamano writes:
> In the next major release Git 2.0 (not *this* one), we will change the
> behavior of the "git push" command.
It's not entirely clear from the formatting whether this sentenece
introduces the whole "Backward
A release candidate Git v1.8.2-rc3 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
3fe30d85cea78a388d61ba79fe3a106fca41cfbe git-1.8.2.rc3.tar.gz
4b378cf6129fa4c9355436b93a69
A release candidate Git v1.8.2-rc2 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
b10a10d8e6351860fde123ffc62081e3800d602c git-1.8.2.rc2.tar.gz
de47a731c9fd426fca6385e2810d
The first release candidate Git v1.8.2-rc1 is now available for
testing at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
44172a71a711b83b4cfaa8e41dd24d05068b0887 git-1.8.2.rc1.tar.gz
fd23a6fd099bf13f8976
Junio C Hamano writes:
> +At Git 2.0 (not *this* one), we
> +plan to change these commands without pathspec to operate on the
> +entire tree, and training your fingers to type "." will protect you
> +against the future change.
My understanding of the plan was more to forbid argumentless git -u|-
Junio C Hamano writes:
>> I don't understand: wasn't this supposed to happen in Git 2.0? Did you
>> mean "In the upcoming major release (tentatively called *2.0*)"?
>
> Thanks. I am not sure what I was thinking. Perhaps when we started
> this cycle we did want to merge the push-2.0-default-to-s
Matthieu Moy writes:
> Junio C Hamano writes:
>
>> Git v1.8.2 Release Notes (draft)
>>
>>
>> Backward compatibility notes
>>
>>
>> In the upcoming major release (tentatively called 1.8.2), we will
>> change the behavior of the "git push" comm
On 2013-02-17 16:52, Junio C Hamano wrote:
> * Color specifiers, e.g. "%C(blue)Hello%C(reset)", used in the
>"--format=" option of "git log" and friends can be disabled when
>the output is not sent to a terminal by prefixing them with
>"auto,", e.g. "%C(auto,blue)Hello%C(auto,reset)".
Junio C Hamano writes:
> Git v1.8.2 Release Notes (draft)
>
>
> Backward compatibility notes
>
>
> In the upcoming major release (tentatively called 1.8.2), we will
> change the behavior of the "git push" command.
>
> When "git push [$there]"
An early preview Git v1.8.2-rc0 for the upcoming release is now
available for testing at the usual places. The preview includes
contributions from 80+ people, totaling some 570+ no-merge changes
since v1.8.1 and should give you more or less a complete picture of
what the upcoming 1.8.2 would look
13 matches
Mail list logo
