On Thu, Feb 5, 2015 at 11:53 PM, Junio C Hamano wrote:
> The latest feature release Git v2.3.0 is now available at the
> usual places.
>
> [...]
> * Git 2.0 was supposed to make the "simple" mode for the default of
>"git push", but it didn't.
>(merge 00a6fa0 jk/push-simple later to maint)
The latest feature release Git v2.3.0 is now available at the
usual places.
This one ended up to be a release with lots of small corrections and
improvements without big uncomfortably exciting features. It is a
lot smaller release than other recent feature releases, consisting
of 255 non-merge com
On 29/01/15 16:52, Jeff King wrote:
Both this and the curl-version issue you reported seem to have simple
solutions that you've already worked out and tested. Would you like to
express them in the form of patches so they can be applied? :)
Patches have been posted as requested.
-tgc
--
To uns
"Tom G. Christensen" writes:
> On 29/01/15 16:43, Jeff King wrote:
>
>> Another option is to just declare that version old and broken, and skip
>> the tests (either by checking its version, or just checking after we
>> import the keys that we can actually _use_ them).
>>
> That would seem a bit h
On 29/01/15 16:43, Jeff King wrote:
Weird. The pubkeys are there in keyring.gpg; I wonder why the older
version of gpg has trouble extracting them (and how one was _supposed_
to export secret keys at that time).
Importing the unmodified keyring.gpg with 1.2.6 yields this:
$ gpg --homedir "$GNU
On Thu, Jan 29, 2015 at 02:30:57PM +0100, Tom G. Christensen wrote:
> On 28/01/15 00:35, Junio C Hamano wrote:
> >A release candidate Git v2.3.0-rc2 is now available for testing
> >at the usual places.
> >
>
> Commit 2cf770 added testing of the --[no-]xmailer option to git send-email
> in t9001-s
On Thu, Jan 29, 2015 at 10:43:20AM -0500, Jeff King wrote:
> It feels a bit hacky, and I wish I knew more about why the current file
> doesn't work (i.e., if we did "gpg --export-secret-keys" with v1.2.6,
> would it produce different output that can be read by both versions?).
> Another option is
On Thu, Jan 29, 2015 at 02:11:05PM +0100, Tom G. Christensen wrote:
> All signed commit tests fail on RHEL4 which is a regression from 2.2.2.
>
> From t4202.42:
>
> ++ git tag -s -m signed_tag_msg signed_tag
> gpg: key CDDE430D: secret key without public key - skipped
> gpg: skipped `C O Mitter
On 28/01/15 00:35, Junio C Hamano wrote:
A release candidate Git v2.3.0-rc2 is now available for testing
at the usual places.
Commit 2cf770 added testing of the --[no-]xmailer option to git
send-email in t9001-send-email.sh
Unfortunately it used the modern Getopt::long style of --no- to
nega
On 28/01/15 00:35, Junio C Hamano wrote:
A release candidate Git v2.3.0-rc2 is now available for testing
at the usual places.
All signed commit tests fail on RHEL4 which is a regression from 2.2.2.
From t4202.42:
++ git tag -s -m signed_tag_msg signed_tag
gpg: key CDDE430D: secret key withou
On 28/01/15 00:35, Junio C Hamano wrote:
A release candidate Git v2.3.0-rc2 is now available for testing
at the usual places.
Building is broken on RHEL4 which is a regression from 2.2.2.
The makefile check for curl >= 7.34.0 fails and enables
USE_CURL_FOR_IMAP_SEND even though curl is 7.12.
A release candidate Git v2.3.0-rc2 is now available for testing
at the usual places.
Hopefully this can become the final v2.3.0 next week, almost as-is.
There are no regression noticed and/or fixed since -rc1, and the
changes are mostly l10n and minor documentation updates.
The tarballs are found
A release candidate Git v2.3.0-rc1 is now available for testing
at the usual places.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/testing/
The following public repositories all have a copy of the 'v2.3.0-rc1'
tag and the 'master' branch that the tag points at:
ur
On Tue, Jan 13, 2015 at 12:57 AM, Junio C Hamano wrote:
> An early preview release Git v2.3.0-rc0 is now available for
> testing at the usual places.
[...]
> Jeff King (38):
[...]
> parse_color: refactor color storage
[...]
I've had this in my .gitconfig since 2010 which was broken by Jeff'
Junio C Hamano writes:
> * "git push" into a repository with a working tree normally refuses
>to modify the branch that is checked out. The command learned to
>optionally do an equivalent of "git reset --hard" only when there
>is no change to the working tree and the index instead,
An early preview release Git v2.3.0-rc0 is now available for
testing at the usual places.
With the slowness from the end-of-year holiday, this cycle turned
out to be a relatively lean one as I predicted (just 200 changes
since 2.2, as opposed to ~500 changes in an normal cycle), but that
is fine.
16 matches
Mail list logo
