Re: [RFC] Questions for "Git User's Survey 2011"

On Wed, Sep 19, 2012 at 7:35 PM, Felipe Contreras wrote: > Hi, > > On Wed, Sep 14, 2011 at 7:39 PM, Jakub Narebski wrote: > >> P.S. Would you be interested in running the next survey? > > I haven't seen any news regarding the 2012 survey. I'm interested in > running the survey this time, but I wo

Message from 'git-rebase'; German translation

As I know how hard translations can be, esp. with that much technical terms inside, I'm usually expecting _not_ to yield the same result when translating a software's translation back to English. However, git-rebase just threw these two sentences at me (And though i know their meaning, i couldn

Re: git clone over http with basic auth bug?

Indeed, thats correct, i should have tried a newer version really before i posted cause i do pull the main git repo and it would have been relatively easy. Newer version did indeed fix the problem. It hadnt occured to me that git-http-backend behaves differently to the "dumb" http protocol on

Re: submodule: if $command was not matched, don't parse other args

Ramkumar Ramachandra writes: > When we try to execute 'git submodule' with an invalid subcommand, we > get an error like the following: > > $ git submodule show > error: pathspec 'show' did not match any file(s) known to git. > Did you forget to 'git add'? > > The cause of the problem

Re: How do I run tests under Valgrind?

Jeff King writes: > On Sat, Sep 22, 2012 at 03:03:58PM +0200, Stefano Lattarini wrote: > >> On 09/21/2012 10:49 PM, Jeff King wrote: >> > >> > Oh. It sounds like setting $SHELL to zsh is really the problem, then. If >> > it is not Bourne-compatible when called as "zsh", then it really should >> >

Re: Quickly searching for a note

Michael J Gruber writes: > On my mental scratch pad (yeah, that's where the bald spots are) I have > the following more general idea to enhance the revision parser: > > --limit-run=

Re: [PATCH] t/test-lib.sh: do not trust $SHELL

Ramkumar Ramachandra writes: > Here's a patch. > > -- 8< -- > From: Ramkumar Ramachandra > Date: Sat, 22 Sep 2012 10:25:10 +0530 > Subject: [PATCH] test-lib: do not trust $SHELL > > Do not trust $SHELL to be a bourne-compatible shell. Instead, use the > Makefile variable $SHELL_PATH. This fixe

Re: How do I run tests under Valgrind?

On 09/22/2012 07:47 PM, Jeff King wrote: > On Sat, Sep 22, 2012 at 03:03:58PM +0200, Stefano Lattarini wrote: > >> On 09/21/2012 10:49 PM, Jeff King wrote: >>> >>> Oh. It sounds like setting $SHELL to zsh is really the problem, then. If >>> it is not Bourne-compatible when called as "zsh", then it

Re: The GitTogether

Hi, > Also, there are many academic institutions, and at least some might > be happy to host an event like this (I'm thinking especially of the Zuse > institute). I had offered to help with hooking up with them several > weeks ago already. So, it's really just a matter of communication. Yep. Ano

Re: How do I run tests under Valgrind?

On Sat, Sep 22, 2012 at 03:03:58PM +0200, Stefano Lattarini wrote: > On 09/21/2012 10:49 PM, Jeff King wrote: > > > > Oh. It sounds like setting $SHELL to zsh is really the problem, then. If > > it is not Bourne-compatible when called as "zsh", then it really should > > be called in a way that tur

Re: Quickly searching for a note

Junio C Hamano venit, vidit, dixit 22.09.2012 01:51: > Jeff King writes: > >> I think people have provided sane techniques for doing this with a >> pipeline. But there is really no reason not to have --grep-notes, just >> as we have --grep. It's simply that nobody has implemented it yet (and >>

[PATCH] graph: avoid infinite loop in graph_show_commit()

The loop can be triggered with "git diff-tree --graph commit" where the commit is a non-merge. It goes like this - graph_show_commit - graph_next_line - graph_output_padding_line The last function quits because graph->commit is NULL, but graph_next_line() does not return "shown", so the loop i

Re: How do I run tests under Valgrind?

On 09/21/2012 10:49 PM, Jeff King wrote: > > Oh. It sounds like setting $SHELL to zsh is really the problem, then. If > it is not Bourne-compatible when called as "zsh", then it really should > be called in a way that turns on compatibility mode (bash will do this > when called as "sh", but you can

Re: What are the ways CRLF files can make it into the repository?

On Fri, Sep 21, 2012 at 01:02:11PM -0600, Joshua Jensen wrote: > We've been running with core.autocrlf = input (some people with > core.autocrlf = true). However, there are some text files in the > repository that are CRLF, and I am at a loss to explain how they go > here. > > We understand that

Re: The GitTogether

Sebastian Schuberth venit, vidit, dixit 21.09.2012 16:33: > On Fri, Sep 21, 2012 at 4:19 PM, Scott Chacon > wrote: > I'm also very much interested in attending a gathering Berlin, though preferably not in the first week of October. As I'm a local, I could probably also help with fi

[PATCH] gitk: Work around empty back and forward images when buttons are disabled

On Mac, the back and forward buttons show an empty rectange instead of a grayed-out arrow when they are disabled. The reason is a Tk bug on Mac that causes disabled images not to draw correctly (not to draw at all, that is); see

[PATCH 2/2] gitk: Highlight first search result immediately on incremental search

When typing in the "Search" field, select the current search result (so that it gets highlighted in orange). This makes it easier to understand what will happen if you then type Ctrl-S. Signed-off-by: Stefan Haller --- gitk | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/

[PATCH 0/2] gitk: Better highlighting of search results

Here's something that has been bugging me for a long time: when using the incremental search feature, it's hard to tell what happens when clicking the Search button (or type Ctrl-S) repeatedly. It does have the concept of a "current" search hit, and Ctrl-S advances to the next one; however, you can

[PATCH 1/2] gitk: Highlight current search hit in orange

When searching for text in the diff, and there are multiple occurrences of the search string, the current one is highlighted in orange, and the other ones in yellow. This makes it much easier to understand what happens when you then click the Search button or hit Ctrl-S repeatedly. Signed-off-by: