Re: What happened to "git status --color=(always|auto|never)"?

> commit 6be4595edb8e5b616c6e8b9fbc78b0f831fa2a87 > Author: Jeff King > Date: Tue Oct 3 09:46:06 2017 -0400 > > color: make "always" the same as "auto" in config > > Would you like to take a stab at adding it? builtin/commit.c and >

Re: What happened to "git status --color=(always|auto|never)"?

On Tue, Oct 10, 2017 at 8:16 AM, Jonathan Nieder <jrnie...@gmail.com> wrote: > Hi, > > Nazri Ramliy wrote: > >> I used to work before, but now: >> >> $ git version >> git version 2.15.0.rc0.39.g2f0e14e649 >> >> $ git status --color=always

What happened to "git status --color=(always|auto|never)"?

I used to work before, but now: $ git version git version 2.15.0.rc0.39.g2f0e14e649 $ git status --color=always error: unknown option `color=always' usage: git status [] [--] ... Is it no longer supported? nazri

Re: Should "git submodule update" accepts --init?

On Thu, May 11, 2017 at 2:42 PM, Junio C Hamano wrote: > I am not a heavy submodule user so what I think may not count, but I > think the "upstream" changing the URL of the submodule should be a > rare and notable event. Making it easy to automatically run "sync" > without

Should "git submodule update" accepts --init?

Hi, The command "git submodule update" accepts an "--init" flag to initialize an uninitialized submodules. Shouldn't it also accept "--sync" flag in order to sync and unsync'd submodule? Otherwise it seems like I'll have to do "git submodule update" twice in order to update an already

Re: [PATCH 1/2] ls-files: adding support for submodules

On Sat, Sep 24, 2016 at 12:34 AM, Stefan Beller wrote: > git -C path/to/sub --keep-prefix ls-files Note that the above can also be written like so (and works identically), due to the fact that -C can be given multiple times: git -C path -C to -C sub --keep-prefix

Re: Why are submodules not automatically handled by default or at least configurable to do so?

On Tue, Oct 27, 2015 at 12:56 AM, Jens Lehmann wrote: > Which seems a bit error prone as you could forget to update the submodules > and build incorrect rpms from them, or am I missing something? For my case I'm not building the rpms directly after merging in the fixes done

Re: Why are submodules not automatically handled by default or at least configurable to do so?

On Mon, Oct 26, 2015 at 7:10 AM, John Smith wrote: > When would people routinely check out a branch and want to stay with the > submodules as > the have been checked out for the old branch? I do this a lot. At my $dayjob we have a super project with bunch of sub projects.

2.6.0: Comment in rebase instruction has become too rigid

Hi, I noticed that the format of the comment lines in a rebase instruction sheet has become stricter - it could no longer begin with spaces or tabs. The comment char ("#" for example) has to appear on the first column. This break my little script (activated via some key binding in my $EDITOR)

[TOY PATCH]: rebase: Add --show-files option

candidates. The files list came from this: git show --raw $sha1|awk '/^:/ {print '${comment_char}'\t$0}' Thoughts? nazri From 4826875c14554d4fa5098ddf9499c33cb7b9001b Mon Sep 17 00:00:00 2001 From: Nazri Ramliy ayieh...@gmail.com Date: Fri, 3 Oct 2014 09:59:38 +0800 Subject: [PATCH] rebase

[PATCH v4] Teach git to change to a given directory using -C option

Hi, Sorry it took me a while to get back on this. Reroll at the bottom ... On Tue, Sep 10, 2013 at 12:32 AM, Junio C Hamano gits...@pobox.com wrote: Nazri Ramliy ayieh...@gmail.com writes: Subject: git: run in a directory given with -C option This is similar in spirit to to make -C dir

Re: [PATCH v3] Teach git to change to a given directory using -C option

On Mon, Sep 09, 2013 at 01:01:33AM -0400, Eric Sunshine wrote: On Sun, Sep 8, 2013 at 9:49 PM, Nazri Ramliy ayieh...@gmail.com wrote: Thanks for the reference. I did read that thread earlier. It doesn't really answer my question, but perhaps it's not terribly important since the interaction

Re: [PATCH v3] Teach git to change to a given directory using -C option

:21:48PM +0800, Nazri Ramliy wrote: diff --git a/Documentation/git.txt b/Documentation/git.txt index 6a875f2..20bba86 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -379,6 +379,9 @@ displayed. See linkgit:git-help[1] for more information, because `git --help

Re: [PATCH v3] Teach git to change to a given directory using -C option

On Wed, Sep 4, 2013 at 6:46 AM, Junio C Hamano gits...@pobox.com wrote: I do not care too deeply either way, but I am curious if there was a reason why you changed the earlier directory to path? Somehow, when we _know_ a path has to be a directory, I find it easier on the readers to spell

Re: [PATCH v3] Teach git to change to a given directory using -C option

On Wed, Sep 04, 2013 at 02:36:47PM +0800, Nazri Ramliy wrote: On Wed, Sep 4, 2013 at 6:46 AM, Junio C Hamano gits...@pobox.com wrote: Does the above format correctly without the usual second and subsequent paragraphs are not indented, but has '+' in place of a blank line? No it doesn't

[PATCH v3] Teach git to change to a given directory using -C option

. for d in d1 d2 d3; do git -C $d svn rebase; done A new test script is added to verify the behavior of this option with other path-related options like --git-dir and --work-tree. Signed-off-by: Nazri Ramliy ayieh...@gmail.com --- Documentation/git.txt | 16 +- git.c | 15

[PATCH v2] Teach git to change to a given directory using -C option

On Sun, Sep 01, 2013 at 12:48:23AM -0400, Eric Sunshine wrote: On Fri, Aug 30, 2013 at 9:35 AM, Nazri Ramliy ayieh...@gmail.com wrote: With this new option, the above can be done with less keystrokes: Grammar: s/less/fewer/ More below... Thanks for taking the time to review this patch

[PATCH] Teach git to change to a given directory using -C option

-by: Nazri Ramliy ayieh...@gmail.com --- This is a reroll of [1]. The only difference is the rewording of the commit message. I'm resending this as I've found it to be useful in my daily git usage in that it helps me stay focused on what I'm doing in the current directory while needing to run git

Re: Does Git now have any C struct version history tracking mechanism?

On Mon, Aug 19, 2013 at 4:37 PM, Thomas Rast tr...@inf.ethz.ch wrote: Hmm, IIUC that's actually not a bug or even a roughness; it's an artifact of how the :pattern:file syntax is defined. It takes the first _funcname line_ matching 'pattern', up to (but excluding) the next funcname line. ...

Re: Does Git now have any C struct version history tracking mechanism?

On Sun, Aug 18, 2013 at 6:33 PM, Zhan Jianyu nasa4...@gmail.com wrote: Such a requirement came into my mind when I am tracking a gloomy C struct , with lengthy list of elements which are either elaborated or opaque. So I use git blame to track it down and found that its original version is

git grep --no-index doesn't do what it says on the tin?

Hi, From git help grep: --no-index Search files in the current directory that is not managed by Git. --untracked In addition to searching in the tracked files in the working tree, search also in untracked files. From the description above I would

[PATCH] Teach git to change to a given directory using -C option

A new test script is added to verify the behavior of this option with other path-related options like --git-dir and --work-tree. Signed-off-by: Nazri Ramliy ayieh...@gmail.com --- Jeff: Thanks for pointing out the mistakes. But I did not address your concern: I know you are copying this from

[PATCH] Teach git to change to a given directory using -C option

This is similar in spirit to to make -C dir ... and tar -C dir Signed-off-by: Nazri Ramliy ayieh...@gmail.com --- Often I find myself needing to find out quickly the status of a repository that is not in my currenct working directory, like this: $ (cd ~/foo; git log -1

Re: [PATCH 0/4] optimizing upload-pack ref peeling

On Thu, Oct 4, 2012 at 5:01 PM, Ævar Arnfjörð Bjarmason ava...@gmail.com wrote: $ time (echo | ~/g/git/git-upload-pack . | pv /dev/null) Totally off-topic, but ... Thanks for making me look up what pv is. I remember checking it out quiet sometime ago and have forgotten about it

Re: Feature request: short cuts for git add /diff etc

On Tue, Sep 4, 2012 at 7:25 PM, Коньков Евгений k...@reg.ru wrote: sot this allow: git diff 1 same asgit diff a1.txt git diff 2 same asgit diff a2.txt git add 1same asgit add a1.txt in case there are may be files with such names I may appply option