Re: bug?: git grep HEAD with exclude in pathspec not taken into account

foo HEAD -- ':!fileA' . HEAD:fileB:foo is false+ > git --no-pager grep foo HEAD -- ':!fileB' . HEAD:fileA:foo HEAD:fileB:foo is false+ Le mer. 24 oct. 2018 à 17:14, Duy Nguyen a écrit : > > On Wed, Oct 24, 2018 at 4:55 PM Christophe Bliard > wrote: > > > > Hi, > > >

Re: bug?: git grep HEAD with exclude in pathspec not taken into account

6410172300120130ustar00rootroot00foo fileB664000161336410172300120170ustar00rootroot00foo is false+ fileA can be excluded, but not fileB. Is it a bug? Thanks -- Christophe Bliard

fatal error when diffing changed symlinks

commit -m 'first' touch d rm c ln -s d c git difftool --dir-diff Thanks for your feedback, Christophe

Re: fatal: bad revision 'git rm -r --ignore-unmatch -- folder'

I've finally found the correct command after some significant research: git filter-branch --tag-name-filter cat --index-filter "git rm -r --cached --ignore-unmatch ${file_path}/${file_name}" --prune-empty --force -- --all On Fri, Jan 20, 2017 at 4:23 PM, jean-christophe manciot &l

Re: fatal: bad revision 'git rm -r --ignore-unmatch -- folder'

Also some context information: Ubuntu 16.10 4.8 git 2.11.0 On Thu, Jan 19, 2017 at 9:32 AM, jean-christophe manciot <actionmysti...@gmail.com> wrote: > In case you were wondering whether these files were tracked or not: > > git-Games# git ls-files Ubuntu/16.04 > Ubuntu/16.04/re

Re: fatal: bad revision 'git rm -r --ignore-unmatch -- folder'

Ubuntu/16.04/scummvm-dbgsym_1.9.0_amd64.deb Ubuntu/16.04/scummvm_1.8.0_amd64.deb Ubuntu/16.04/scummvm_1.9.0_amd64.deb On Tue, Jan 17, 2017 at 4:30 PM, jean-christophe manciot <actionmysti...@gmail.com> wrote: > Hi there, > > I'm trying to purge a complete folder and its files from t

fatal: bad revision 'git rm -r --ignore-unmatch -- folder'

.deb* ... -rw-r--r-- 1 actionmystique actionmystique 67382492 Oct 13 09:15 scummvm-dbgsym_1.9.0_amd64.deb What is going on? -- Jean-Christophe

Re: Gitk cannot start in the latest version when using --all

Le 29/09/2015 15:49, Konstantin Khomoutov a écrit : On Tue, 29 Sep 2015 15:40:55 +0200 Christophe COEVOET <s...@notk.org> wrote: I'm installing git and gitk from the Ubuntu PPA maintained by the Git team. I received the Git 2.6 update today. Since this update, I'm unable to launc

Gitk cannot start in the latest version when using --all

ot;/usr/bin/gitk" line 12442) Launching gitk without the --all option works fine. Launching gitk with the --branches option or the --tags option is also broken -- Christophe Coevoet -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a messa

git-remote-hg

Hi, I am using git-remote-hg to access to projects on bitbucket. I can clone the master branch fine and push to it. I also see hg branches as remotes/origin/branches/«branch». However, if I create a local branch branches/x and want to push it to remotes/origin/branches/x, it gets pushed to the