Re: Installing git binaries on a non-default directory (Ubuntu)

Gianpaolo Macario writes: > By some googling and after reading the git sources and the commit logs I > assumed that the `RUNTIME_PREFIX` option > (see ) was designed for > that purpose, I do not think so. The standard procedure to stage into

Re: When and how to to contact the Git developers (gist)

Thomas Ferris Nicolaisen writes: > At the Dev Summit, I mentioned this gist I've got lined up for > whenever someone should consider sending an email to this list: > > https://gist.github.com/tfnico/4441562 > > It's a handy link to share in some encounters, exemplified by Konstantin here: > > htt

Re: Feature request: implement '--follow' option for `git blame`

Eugen Konkov writes: > I agree with your complex example. Note that it is a norm, not anything complex, that we do not rename a file wholesale. > But it will be great to guess in simple case, when in version v1.0 > only one file A which were renamed into C half year later. So you used to have

Re: [PATCH v2] CodingGuidelines: updating 'rough' rule count

On Mon, Apr 13, 2015 at 1:00 AM, Eric Sunshine wrote: > On Mon, Apr 13, 2015 at 12:26 AM, Julian Gindi wrote: >> Changed inaccurate count of "rough rules" from three to the more >> generic 'a few'. > > Imperative: s/Changed/Change/ I forgot to mention the unusual 2-space indentation of t

Re: [PATCH v2] CodingGuidelines: updating 'rough' rule count

On Mon, Apr 13, 2015 at 12:26 AM, Julian Gindi wrote: > CodingGuidelines: updating 'rough' rule count Imperative mood is preferred, so "update" rather than "updating": CodingGuidelines: update 'rough' rule count > Changed inaccurate count of "rough rules" from three to the more > ge

Re: [PATCH v2 2/5] log: honor log.merges= option

Koosha Khajehmoogahi writes: > On 04/08/2015 04:28 AM, Junio C Hamano wrote: > >> It is strange that you have to ask me to give you the reason why you >> chose it that way, isn't it? > > AFAIK, the only other command that supports --merges and --no-merges options > is > rev-list. This new featur

Re: [PATCH v2] CodingGuidelines: updating 'rough' rule count

Changed inaccurate count of "rough rules" from three to the more generic 'a few'. --- Documentation/CodingGuidelines | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines index 0f8cccf..2dd35bd 100644 --- a/Docum

Re: [PATCH 0/2] git-p4: Improve client path detection

Vitor Antunes writes: > Luke Diamand wrote on Sun, 05 Apr 2015 20:27:11 +0100 >> On 28/03/15 12:28, Vitor Antunes wrote: >> > I'm adding a test case for a scenario I was confronted with when using >> > branch >> > detection and a client view specification. It is possible that the >> > implemen

Re: [PATCH] CodingGuidelines: updating 'rough' rule count

On Sun, Apr 12, 2015 at 7:47 PM, Julian Gindi wrote: > Changed inaccurate count of "rough rules" from three to four. > > Signed-off-by: Julian Gindi > --- > diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines > index 0f8cccf..c422ecd 100644 > --- a/Documentation/CodingGui

[PATCH] CodingGuidelines: updating 'rough' rule count

Changed inaccurate count of "rough rules" from three to four. Signed-off-by: Julian Gindi --- Documentation/CodingGuidelines | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines index 0f8cccf..c422ecd 100644 --- a/Doc

[PATCH] gitweb: Update logo and favicon

The new images were downloaded from https://git-scm.herokuapp.com/downloads/logos and converted with ImageMagick: convert -resize 72x30 Git-Logo-2Color.eps git-logo.png convert -resize 16x16 Git-Icon-1788C.eps git-favicon.png The old logo was only 27 pixels in height, the 3 additional pixels a

Re: Draft of Git Rev News edition 2

On Sun, Apr 12, 2015 at 9:03 PM, Christian Couder wrote: > A draft of Git Rev News edition 2 is available here: > > https://github.com/git/git.github.io/blob/master/rev_news/draft/edition-2.md There's also a "secret" live preview here now: http://git.github.io/rev_news/draft/edition-2 Btw, I've

Draft of Git Rev News edition 2

Hi, A draft of Git Rev News edition 2 is available here: https://github.com/git/git.github.io/blob/master/rev_news/draft/edition-2.md Everyone is welcome to contribute in any section either by editing the above page on GitHub and sending a pull request, or by commenting on this GitHub issue: ht

Re: [msysGit] Re: Sneak peek of the upcoming Git for Windows 2.x

Hi Rupert, On 2015-04-11 10:37, rupert thurner wrote: > > three things i do not like it so much: > * the old distinct icon is replaced by a new one which looks similar to > many other programs, like google chrome. would it be possible to set the > old icon? Git 1.9.5 came with the Git icon alr

Re: [PATCH v2 2/3] p7300: add performance tests for clean

On 04/12, erik elfström wrote: > On Sat, Apr 11, 2015 at 7:59 PM, Thomas Gummerer wrote: > > On 04/11, Erik Elfström wrote: > >> Signed-off-by: Erik Elfström > >> --- > >> t/perf/p7300-clean.sh | 37 + > >> 1 file changed, 37 insertions(+) > >> create mode 10

Re: [PATCH v2 2/3] p7300: add performance tests for clean

On Sat, Apr 11, 2015 at 7:59 PM, Thomas Gummerer wrote: > On 04/11, Erik Elfström wrote: >> Signed-off-by: Erik Elfström >> --- >> t/perf/p7300-clean.sh | 37 + >> 1 file changed, 37 insertions(+) >> create mode 100755 t/perf/p7300-clean.sh >> >> diff --git a

Re: How to send a warning message from git hosting server?

On Wed, Apr 8, 2015 at 8:08 PM, Tony Finch wrote: > Yi, EungJun wrote: >> >> I want a way to response a remote message when a client send any kind >> of request. Is it possible? > > Yes, though you need a wrapper around git. Recent versions of gitolite > have a "motd" message of the day feature.

Re: Possible Bug in git-http-push

Am 10.04.2015 um 18:55 schrieb Thomas Braun: > Am 10.04.2015 um 13:15 schrieb Stefan: >> Hello List >> >> I possibly found a bug in git-http-push: >> >> When I push my local repo via http secured with basic authorization, >> then i get: >> >> error: Cannot access URL https://example.ch/example_repo

[PATCH 2/7] attr.c: replace home_config_paths() with xdg_config_home()

Since only the xdg attributes file path is required, simplify the code by using xdg_config_home() instead of home_config_paths(). Signed-off-by: Paul Tan --- attr.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/attr.c b/attr.c index 1f9eebd..868dce3 100644 --- a/attr

[PATCH 5/7] git-commit: replace use of home_config_paths()

Since home_config_paths() combines two distinct functionality already implemented by expand_user_path() and xdg_config_home(), and hides the home config file path ~/.gitconfig. Make the code more explicit by replacing the use of home_config_paths() with expand_user_path() and xdg_config_home(). Si

[PATCH 6/7] git-config: replace use of home_config_paths()

Since home_config_paths() combines distinct functionality already implemented by expand_user_path() and xdg_config_home(), and hides the home config file path ~/.gitconfig. Make the code more explicit by replacing the use of home_config_paths() with expand_user_path() and xdg_config_home(). Signed

[PATCH 3/7] dir.c: replace home_config_paths() with xdg_config_home()

Since only the xdg excludes file path is required, simplify the code by replacing use of home_config_paths() with xdg_config_home(). Signed-off-by: Paul Tan --- dir.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/dir.c b/dir.c index 0943a81..335dc7e 100644 --- a/dir.

[PATCH 7/7] path.c: remove home_config_paths()

home_config_paths() combines distinct functionality already implemented by expand_user_path() and xdg_config_home(), and it also hard-codes the path ~/.gitconfig, which makes it unsuitable to use for other home config file paths. Since its use will just add unnecessary complexity to the code, remov

[PATCH 4/7] credential-store.c: replace home_config_paths() with xdg_config_home()

Since only the xdg credentials file path is required, and home_config_paths() is unable to construct the path ~/.git-credentials, simplify the code by replacing home_config_paths() with xdg_config_home(). Signed-off-by: Paul Tan --- credential-store.c | 2 +- 1 file changed, 1 insertion(+), 1 de

[PATCH 1/7] path.c: implement xdg_config_home()

The XDG base dir spec[1] specifies that configuration files be stored in a subdirectory in $XDG_CONFIG_HOME. To construct such a configuration file path, home_config_paths() can be used. However, home_config_paths() combines distinct functionality: 1. Retrieve the home git config file path ~/.gitc