Re: [ANNOUNCE] Git v2.1.0
On 15/08/14 23:46, Junio C Hamano wrote: The latest feature release Git v2.1.0 is now available at the usual places. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.1.0' tag and the 'master' branch that the tag points at: url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Are you going to tag and push v2.1.0 to the documentation repos? (I have been watching the kernel.org documentation repos - should I be looking elsewhere?) I stopped building the documentation myself when my documentation toolchain got a bit old. I have upgraded to Linux Mint 17 since then, so my toolchain may be up to the job now, so perhaps I should build it myself. ;-) ATB, Ramsay Jones -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [ANNOUNCE] Git v2.1.0
Theodore Ts'o ty...@mit.edu writes: On Fri, Aug 15, 2014 at 03:46:29PM -0700, Junio C Hamano wrote: The latest feature release Git v2.1.0 is now available at the usual places. I pulled down git v2.1.0, and when I tried to build it via: make prefix=/usr/local profile-fast The build died with this: cannot open test-results/p5302-pack-index.subtests: No such file or directory at ./aggregate.perl line 77. Makefile:7: recipe for target 'perf' failed make[2]: *** [perf] Error 2 make[2]: Leaving directory '/usr/projects/git/git/t/perf' Not a big deal, but I thought I would mention it. Thanks. But this does not seem to reproduce for me (note: I never build profile-anything myself so I may not be seeing the error even there is---the only thing I checked was the lack of make errors). We did have changes to profile-feedback build during this round: $ git shortlog 3b3b61c^..3b3b61c^2 Andi Kleen (4): Use BASIC_FLAGS for profile feedback Don't define away __attribute__ on gcc Run the perf test suite for profile feedback too Fix profile feedback with -jN and add profile-fast I admit I didn't try -jN, and if there are leaky dependencies in the last patch, it may explain the symptom. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [ANNOUNCE] Git v2.1.0
Ramsay Jones ram...@ramsay1.demon.co.uk writes: Are you going to tag and push v2.1.0 to the documentation repos? I forgot to do the documentation build (which used to be triggered from post-receive hook at k.org and never had the risk of anybody forgetting, but it is all manual now---progress X-) yesterday. It is pushed out now. Thanks. This is a tangent, but I probahbly should start talking with k.org folks about arranging to keep the preformatted individual manual pages (not the tarball that your messages is about) up-to-date. The last time I checked, their file-upload procedure these days are geared towards the use case to upload a handful of tarballs and I haven't found a way that is not too cumbersome to update a directory tree with hundreds of individual files. For now, https://git-htmldocs.googlecode.com/git/git.html would do, but I'd prefer to have at least two sites to publish to, and k.org is the natural other candidate. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ANNOUNCE] Git v2.1.0
The latest feature release Git v2.1.0 is now available at the usual places. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.1.0' tag and the 'master' branch that the tag points at: url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git v2.1 Release Notes == Backward compatibility notes * The default value we give to the environment variable LESS has been changed from FRSX to FRX, losing S (chop long lines instead of wrapping). Existing users who prefer not to see line-wrapped output may want to set $ git config core.pager less -S to restore the traditional behaviour. It is expected that people find output from most subcommands easier to read with the new default, except for blame which tends to produce really long lines. To override the new default only for git blame, you can do this: $ git config pager.blame less -S * A few disused directories in contrib/ have been retired. Updates since v2.0 -- UI, Workflows Features * Since the very beginning of Git, we gave the LESS environment a default value FRSX when we spawn less as the pager. S (chop long lines instead of wrapping) has been removed from this default set of options, because it is more or less a personal taste thing, as opposed to the others that have good justifications (i.e. R is very much justified because many kinds of output we produce are colored and FX is justified because output we produce is often shorter than a page). * The logic and data used to compute the display width needed for UTF-8 strings have been updated to match Unicode 7.0 better. * HTTP-based transports learned to better propagate the error messages from the webserver to the client coming over the HTTP transport. * The completion script for bash (in contrib/) has been updated to better handle aliases that define a complex sequence of commands. * The core.preloadindex configuration variable is enabled by default, allowing modern platforms to take advantage of their multiple cores. * git clone applies the if cloning from a local disk, physically copy the repository using hardlinks, unless otherwise told not to with --no-local optimization when the url.*.insteadOf mechanism rewrites a remote-repository git clone $URL into a clone from a local disk. * git commit --date=date option learned more timestamp formats, including --date=now. * The `core.commentChar` configuration variable is used to specify a custom comment character (other than the default #) for the commit message editor. This can be set to `auto` to attempt to choose a different character that does not conflict with any that already starts a line in the message being edited, for cases like git commit --amend. * git format-patch learned --signature-file=file to add the contents of a file as a signature to the mail message it produces. * git grep learned the grep.fullname configuration variable to force --full-name to be the default. This may cause regressions for scripted users who do not expect this new behaviour. * git imap-send learned to ask the credential helper for auth material. * git log and friends now understand the value auto for the log.decorate configuration variable to enable the --decorate option automatically when the output is sent to tty. * git merge without an argument, even when there is an upstream defined for the current branch, refused to run until merge.defaultToUpstream is set to true. Flip the default of that configuration variable to true. * git mergetool learned to drive the vimdiff3 backend. * mergetool.prompt used to default to 'true', always asking do you really want to run the tool on this path?. The default has been changed to 'false'. However, the prompt will still appear if mergetool used its autodetection system to guess which tool to use. Users who explicitly specify or configure a tool will no longer see the prompt by default. Strictly speaking, this is a backward incompatible change and users need to explicitly set the variable to 'true' if they want to be prompted to confirm running the tool on each path. * git replace learned the --edit subcommand to create a replacement by editing an existing object. * git replace learned a --graft option to rewrite the parents of a commit. * git send-email learned --to-cover and --cc-cover options, to tell it to copy To: and Cc: headers found in the first input file when emitting later input files. * git svn learned to
Re: [ANNOUNCE] Git v2.1.0
On Fri, Aug 15, 2014 at 03:46:29PM -0700, Junio C Hamano wrote: The latest feature release Git v2.1.0 is now available at the usual places. I pulled down git v2.1.0, and when I tried to build it via: make prefix=/usr/local profile-fast The build died with this: cannot open test-results/p5302-pack-index.subtests: No such file or directory at ./aggregate.perl line 77. Makefile:7: recipe for target 'perf' failed make[2]: *** [perf] Error 2 make[2]: Leaving directory '/usr/projects/git/git/t/perf' Not a big deal, but I thought I would mention it. Cheers, - Ted -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ANNOUNCE] Git v2.1.0-rc2
A release candidate Git v2.1.0-rc2 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.1.0-rc2' tag and the 'master' branch that the tag points at: url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git v2.1 Release Notes (draft) == Backward compatibility notes * The default value we give to the environment variable LESS has been changed from FRSX to FRX, losing S (chop long lines instead of wrapping). Existing users who prefer not to see line-wrapped output may want to set $ git config core.pager less -S to restore the traditional behaviour. It is expected that people find output from most subcommands easier to read with the new default, except for blame which tends to produce really long lines. To override the new default only for git blame, you can do this: $ git config pager.blame less -S * A few disused directories in contrib/ have been retired. Updates since v2.0 -- UI, Workflows Features * Since the very beginning of Git, we gave the LESS environment a default value FRSX when we spawn less as the pager. S (chop long lines instead of wrapping) has been removed from this default set of options, because it is more or less a personal taste thing, as opposed to the others that have good justifications (i.e. R is very much justified because many kinds of output we produce are colored and FX is justified because output we produce is often shorter than a page). * The logic and data used to compute the display width needed for UTF-8 strings have been updated to match Unicode 7.0 better. * HTTP-based transports learned to better propagate the error messages from the webserver to the client coming over the HTTP transport. * The completion script for bash (in contrib/) has been updated to better handle aliases that define a complex sequence of commands. * The core.preloadindex configuration variable is enabled by default, allowing modern platforms to take advantage of their multiple cores. * git clone applies the if cloning from a local disk, physically copy the repository using hardlinks, unless otherwise told not to with --no-local optimization when the url.*.insteadOf mechanism rewrites a remote-repository git clone $URL into a clone from a local disk. * git commit --date=date option learned more timestamp formats, including --date=now. * The `core.commentChar` configuration variable is used to specify a custom comment character (other than the default #) for the commit message editor. This can be set to `auto` to attempt to choose a different character that does not conflict with any that already starts a line in the message being edited, for cases like git commit --amend. * git format-patch learned --signature-file=file to add the contents of a file as a signature to the mail message it produces. * git grep learned the grep.fullname configuration variable to force --full-name to be the default. This may cause regressions for scripted users who do not expect this new behaviour. * git imap-send learned to ask the credential helper for auth material. * git log and friends now understand the value auto for the log.decorate configuration variable to enable the --decorate option automatically when the output is sent to tty. * git merge without an argument, even when there is an upstream defined for the current branch, refused to run until merge.defaultToUpstream is set to true. Flip the default of that configuration variable to true. * git mergetool learned to drive the vimdiff3 backend. * mergetool.prompt used to default to 'true', always asking do you really want to run the tool on this path?. The default has been changed to 'false'. However, the prompt will still appear if mergetool used its autodetection system to guess which tool to use. Users who explicitly specify or configure a tool will no longer see the prompt by default. Strictly speaking, this is a backward incompatible change and users need to explicitly set the variable to 'true' if they want to be prompted to confirm running the tool on each path. * git replace learned the --edit subcommand to create a replacement by editing an existing object. * git replace learned a --graft option to rewrite the parents of a commit. * git send-email learned --to-cover and --cc-cover options, to tell it to copy To: and Cc: headers found in the first input file when emitting later
Re: [ANNOUNCE] Git v2.1.0-rc1
Ramsay Jones ram...@ramsay1.demon.co.uk writes: On 04/08/14 23:31, Junio C Hamano wrote: * The leaf function to check validity of a refname format has been micro-optimized, using SSE2 instructions when available. A few breakages during its development have been caught and fixed already but there might remain some more still; please test and report if you find any. This has been removed. Thanks for a reminder. Will drop. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [ANNOUNCE] Git v2.1.0-rc1
On 14-08-04 06:31 PM, Junio C Hamano wrote: * git grep learned grep.fullname configuration variable to force --full-name to be default. This may cause regressions on scripted users that do not expect this new behaviour. Should this be noted in the backward compatibility notes? M. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [ANNOUNCE] Git v2.1.0-rc1
Marc Branchaud marcn...@xiplink.com writes: On 14-08-04 06:31 PM, Junio C Hamano wrote: * git grep learned grep.fullname configuration variable to force --full-name to be default. This may cause regressions on scripted users that do not expect this new behaviour. Should this be noted in the backward compatibility notes? I debated it myself, but decided that it was minor enough (in the sense that it is obvious when it breaks and it also is obvious how to adjust the script in a way that is also compatible with older versions of Git). Thanks for a careful reading. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ANNOUNCE] Git v2.1.0-rc1
v2.1.0-rc1, the first release candidate Git for v2.1, 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.1.0-rc1' tag and the 'master' branch that the tag points at: url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git v2.1 Release Notes (draft) == Backward compatibility notes * The default value we give to the environment variable LESS has been changed from FRSX to FRX, losing S (chop long lines instead of wrapping). Existing users who prefer not to see line-wrapped output may want to set $ git config core.pager less -S to restore the traditional behaviour. It is expected that people find output from the most subcommands easier to read with the new default, except for blame which tends to produce really long lines. To override the new default only for git blame, you can do this: $ git config pager.blame less -S * A few disused directories in contrib/ have been retired. Updates since v2.0 -- UI, Workflows Features * Since the very beginning of Git, we gave the LESS environment a default value FRSX when we spawn less as the pager. S (chop long lines instead of wrapping) has been removed from this default set of options, because it is more or less a personal taste thing, as opposed to others that have good justifications (i.e. R is very much justified because many kinds of output we produce are colored and FX is justified because output we produce is often shorter than a page). * The logic and data used to compute the display width needed for UTF-8 strings have been updated to match Unicode 7.0 better. * HTTP-based transports learned to propagate the error messages from the webserver better to the client coming over the HTTP transport. * The completion script for bash (in contrib/) has been updated to handle aliases that define complex sequence of commands better. * The core.preloadindex configuration variable is by default enabled, allowing modern platforms to take advantage of the multiple cores they have. * git clone applies the if cloning from a local disk, physically copy repository using hardlinks, unless otherwise told not to with --no-local optimization when url.*.insteadOf mechanism rewrites a git clone $URL that refers to a repository over the network to a clone from a local disk. * git commit --date=date option learned to read from more timestamp formats, including --date=now. * The `core.commentChar` configuration variable is used to specify a custom comment character other than the default # to be used in the commit log editor. This can be set to `auto` to attempt to choose a different character that does not conflict with what already starts a line in the message being edited for cases like git commit --amend. * git format-patch learned --signature-file=file to take the mail signature from. * git grep learned grep.fullname configuration variable to force --full-name to be default. This may cause regressions on scripted users that do not expect this new behaviour. * git imap-send learned to ask the credential helper for auth material. * git log and friends now understand the value auto set to the log.decorate configuration variable to enable the --decorate option automatically when the output is sent to tty. * git merge without argument, even when there is an upstream defined for the current branch, refused to run until merge.defaultToUpstream is set to true. Flip the default of that configuration variable to true. * git mergetool learned to drive the vimdiff3 backend. * mergetool.prompt used to default to 'true', always asking do you really want to run the tool on this path?. Among the two purposes this prompt serves, ignore the use case to confirm that the user wants to view particular path with the named tool, and redefine the meaning of the prompt only to confirm the choice of the tool made by the autodetection (for those who configured the tool explicitly, the prompt shown for the latter purpose is simply annoying). Strictly speaking, this is a backward incompatible change and the users need to explicitly set the variable to 'true' if they want to resurrect the now-ignored use case. * git replace learned the --edit subcommand to create a replacement by editing an existing object. * git replace learned a --graft option to rewrite parents of a commit. * git send-email learned --to-cover and --cc-cover
Re: [ANNOUNCE] Git v2.1.0-rc1
On 04/08/14 23:31, Junio C Hamano wrote: v2.1.0-rc1, the first release candidate Git for v2.1, is now [snip] * The leaf function to check validity of a refname format has been micro-optimized, using SSE2 instructions when available. A few breakages during its development have been caught and fixed already but there might remain some more still; please test and report if you find any. This has been removed. ATB, Ramsay Jones -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ANNOUNCE] Git v2.1.0-rc0
An early preview release Git v2.1.0-rc0 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.1.0-rc0' tag and the 'master' branch that the tag points at: url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git v2.1 Release Notes (draft) == Backward compatibility notes * The default value we give to the environment variable LESS has been changed from FRSX to FRX, losing S (chop long lines instead of wrapping). Existing users who prefer not to see line-wrapped output may want to set $ git config core.pager less -S to restore the traditional behaviour. It is expected that people find output from the most subcommands easier to read with the new default, except for blame which tends to produce really long lines. To override the new default only for git blame, you can do this: $ git config pager.blame less -S * A few disused directories in contrib/ have been retired. Updates since v2.0 -- UI, Workflows Features * Since the very beginning of Git, we gave the LESS environment a default value FRSX when we spawn less as the pager. S (chop long lines instead of wrapping) has been removed from this default set of options, because it is more or less a personal taste thing, as opposed to others that have good justifications (i.e. R is very much justified because many kinds of output we produce are colored and FX is justified because output we produce is often shorter than a page). * The logic and data used to compute the display width needed for UTF-8 strings have been updated to match Unicode 7.0 better. * HTTP-based transports learned to propagate the error messages from the webserver better to the client coming over the HTTP transport. * The completion script for bash (in contrib/) has been updated to handle aliases that define complex sequence of commands better. * The core.preloadindex configuration variable is by default enabled, allowing modern platforms to take advantage of the multiple cores they have. * git clone applies the if cloning from a local disk, physically copy repository using hardlinks, unless otherwise told not to with --no-local optimization when url.*.insteadOf mechanism rewrites a git clone $URL that refers to a repository over the network to a clone from a local disk. * git commit --date=date option learned to read from more timestamp formats, including --date=now. * The `core.commentChar` configuration variable is used to specify a custom comment character other than the default # to be used in the commit log editor. This can be set to `auto` to attempt to choose a different character that does not conflict with what already starts a line in the message being edited for cases like git commit --amend. * git format-patch learned --signature-file=file to take the mail signature from. * git grep learned grep.fullname configuration variable to force --full-name to be default. This may cause regressions on scripted users that do not expect this new behaviour. * git imap-send learned to ask the credential helper for auth material. * git log and friends now understand the value auto set to the log.decorate configuration variable to enable the --decorate option automatically when the output is sent to tty. * git merge without argument, even when there is an upstream defined for the current branch, refused to run until merge.defaultToUpstream is set to true. Flip the default of that configuration variable to true. * git mergetool learned to drive the vimdiff3 backend. * mergetool.prompt used to default to 'true', always asking do you really want to run the tool on this path?. Among the two purposes this prompt serves, ignore the use case to confirm that the user wants to view particular path with the named tool, and redefine the meaning of the prompt only to confirm the choice of the tool made by the autodetection (for those who configured the tool explicitly, the prompt shown for the latter purpose is simply annoying). Strictly speaking, this is a backward incompatible change and the users need to explicitly set the variable to 'true' if they want to resurrect the now-ignored use case. * git replace learned the --edit subcommand to create a replacement by editing an existing object. * git replace learned a --graft option to rewrite parents of a commit. * git send-email learned --to-cover and --cc-cover options, to tell
