Bug in update-index man page

I've noticed the following text in the documentation pages for the `update-index` command: Files to act on. Note that files beginning with . are discarded. This includes ./file and dir/./file. If you don't want this, then use cleaner names. The same applies to

Re: Remove help advice text from git editors for interactive rebase and reword

> On 24 Jul 2017, at 01:09 , Junio C Hamano wrote: > > Who is running "git commit --amend" and "git rebase -i" in the > workflow of a user of your tool? Is it the end user who types these > commands to the shell command prompt, or does your tool formulate > the command line

Remove help advice text from git editors for interactive rebase and reword

Hello, is it possible to remove the helping text which appears at the bottom of the Git interactive rebase editor (the one with the list of instructions), and the one which appears at the bottom of the commit editor (which appears on rewording a commit or squashing commits)? The texts I'm

Re: How to add custom metadata to Git commit object

gits...@pobox.com> wrote: > > Jeff King <p...@peff.net> writes: > >> On Mon, May 30, 2016 at 08:58:08PM +0300, Kirill Likhodedov wrote: >> ... >>> There are git-notes, which could be used for the purpose, but they are >>> visible to the user via stand

How to add custom metadata to Git commit object

Is it possible to add custom metadata to Git commit object? Such metadata should be ignored by Git commands, but could be used by a 3-party tool which knows the format and knows where to look. I assume that this should be possible, given that Git objects are actually patches, and patches can

How to have EOL=LF and keep binary files auto-detection?

Hi, I wonder if it is possible both to have LFs in all and only text files in working trees, and keep Git’s binary files auto-detection? To be more precise: * we want all text files to be checked out in LF; * we don’t want force people to set “core.autocrlf” to false, preferring to keep this

git worktree fails to recreate existing branch even with -B

Git doesn’t allow me to execute git worktree add -B where already exists in the repository. The command prints the following: Preparing (identifier ) fatal: Refusing to point HEAD outside of refs/ I’m trying to create a worktree on an existing branch , which should point to .

Re: git show doesn't work on file names with square brackets

Hi Johannes, > On 06 Feb 2016, at 19:10 , Johannes Schindelin > wrote: > > git show 'HEAD:bra[ckets].txt' -- > Nice catch! It works for me even without quotes. Although this “--“ is mentioned in the error message, I didn’t even try since its meaning is

Re: git show doesn't work on file names with square brackets

Hi Duy, > It's from 28fcc0b (pathspec: avoid the need of "--" when wildcard is > used - 2015-05-02) v2.5.0 is the first release which contains 28fcc0b. I can confirm that older versions of Git work correctly without “--“: # /opt/local/bin/git version git version 1.7.1.1 # /opt/local/bin/git

git show doesn't work on file names with square brackets

I’ve faced a problem that `git show :` returns an error when contains square brackets. Interestingly, the problem is reproducible on "GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin15)", but not on "zsh 5.0.7 (x86_64-pc-linux-gnu)”. The problem is also reproducible when called from a

Re: git show doesn't work on file names with square brackets

Hi Johannes, thanks for your answer, but unfortunately it doesn’t help. > On 06 Feb 2016, at 17:21 , Johannes Schindelin > wrote: > > This is expected behavior of the Bash you are using. The commands that I > think would reflect your intentions would be: > >

Default ordering of git log output

Is it intended behavior that the default git log output (without ordering parameters) can show parents before children? The man says: Commit Ordering By default, the commits are shown in reverse chronological order. so it tells nothing about parent-to-child relationship. I‘ve just

git log date filter behavior with --date-order

Hi, I’ve faced a strange behavior when filtering git log by date. When used with “--date-order” it gives significantly less results that when used without that option: # git log --pretty=oneline --remotes --after=Wed May 20 23:00:00 MSK 2015 --before=Fri May 22 00:00:00 MSK 2015 -- | wc -l

Is it possible to list unpushed tags without accessing remote?

Hi, is it possible to know which tags are not yet pushed to a remote via a completely local command? (e.g. the list of unpushed _commits_ may be received by ‘git log upstream..’) I know it is possible to execute 'git ls-remote’ or 'git push --dry-run’, but both ask the remote server. I’m

Re: Is it possible to list unpushed tags without accessing remote?

On 26 Jun 2014, at 23:04 , Junio C Hamano gits...@pobox.com wrote: Andreas Schwab sch...@linux-m68k.org writes: Not by default, but it is easy to configure your clone to fetch tags to a separate namespace. But then in order to learn what tags the remote has, you need to talk to the

Re: Get all tips quickly

and the various options it has? Doing this for 35k tags is still going to be non-trivial. On 13 Apr 2014, at 23:20 , Michael Haggerty mhag...@alum.mit.edu wrote: On 04/13/2014 04:19 PM, Kirill Likhodedov wrote: What is fastest possible way to get all “tips” (leafs of the Git log graph) in a Git

Get all tips quickly

they point to (unlike .git/packed-refs). And that’s a pity that `git tag` doesn’t show the hashes. Thanks a lot for any help! - Kirill Likhodedov JetBrains http://www.jetbrains.com Develop with pleasure! -- To unsubscribe from this list: send the line unsubscribe git in the body of a message

Re: git log --no-walk --tags produces strange result for certain user

Hi everybody, I received one more complaint for this issue, and now it appears in a public repository https://github.com/spray/spray To reproduce: # git clone https://github.com/spray/spray # cd spray # git log --no-walk --tags --pretty=%H %d --decorate=full | tail -3

git log --no-walk --tags produces strange result for certain user

Hey, I use the following commands to receive the list of tags together with hashes the point to: git log --tags --no-walk --format=%H%d%x01 --decorate=full Generally it works fine, however a user reported that for his repository this command returns the list containing several hashes

Re: Bug? git show behaves incorrectly when called on a stash object

On 20.03.2013, at 19:56, Matthieu Moy wrote: stash objects are commits with 2 parents (ie. merge commits). One commit is the HEAD you stashed from, and the other is the saved state of the index. ... Use git show --first-parent --name-status, it should do what you expect Thanks a lot for

Bug? git show behaves incorrectly when called on a stash object

05aa170746dc4e060f10710a92aed4592276f2d4 Merge: 737f544 7c2160f Author: Kirill Likhodedov kirill.likhode...@gmail.com Date: Wed Mar 20 18:56:28 2013 +0400 WIP on master: 737f544 master MM conflict.js - The first gives the correct result, while the second

Set core.ignorecase globally

to confusions when renaming a file by changing only the case of letters). -- Kirill Likhodedov JetBrains, Inc http://www.jetbrains.com Develop with pleasure! -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord