git name-rev --exclude is not available in git <2.13 - breaking commit history #5560

New Issue

GiteaMirror · 2025-11-02T06:29:00-06:00

GiteaMirror commented

2025-11-02 06:29:00 -06:00

Originally created by @Ulyev-ad on GitHub (Jun 16, 2020).

I can't view the commit history, error.

Error:

In logs:
2020/06/16 23:49:56 ...uters/repo/commit.go:311:Diff() [E] commit.GetBranchName: exit status 129 - error: unknown option exclude'
usage: git name-rev [options] ...
or: git name-rev [options] --all
or: git name-rev [options] --stdin

    --name-only           print only names (no SHA-1)
    --tags                only use tags to name the commits
    --refs <pattern>      only use refs matching <pattern>

    --all                 list all commits reachable from all refs
    --stdin               read from stdin
    --undefined           allow to print `undefined` names
    --always              show abbreviated commit object as fallback

`

Originally created by @Ulyev-ad on GitHub (Jun 16, 2020). I can't view the commit history, error. ![image](https://user-images.githubusercontent.com/13260152/84827233-33fa0500-b035-11ea-8ad4-01b1d5c20e48.png) Error: ![image](https://user-images.githubusercontent.com/13260152/84827290-4aa05c00-b035-11ea-8db1-7334b718187e.png) In logs: `2020/06/16 23:49:56 ...uters/repo/commit.go:311:Diff() [E] commit.GetBranchName: exit status 129 - error: unknown option `exclude' usage: git name-rev [options] <commit>... or: git name-rev [options] --all or: git name-rev [options] --stdin --name-only print only names (no SHA-1) --tags only use tags to name the commits --refs <pattern> only use refs matching <pattern> --all list all commits reachable from all refs --stdin read from stdin --undefined allow to print `undefined` names --always show abbreviated commit object as fallback `

GiteaMirror closed this issue

2025-11-02 06:29:00 -06:00

GiteaMirror commented

2025-11-02 06:29:01 -06:00

@zeripath commented on GitHub (Jun 16, 2020):

What version of git do you have?

@zeripath commented on GitHub (Jun 16, 2020): What version of git do you have?

GiteaMirror commented

2025-11-02 06:29:01 -06:00

@Ulyev-ad commented on GitHub (Jun 16, 2020):

Oh, I forgot to update. Yes, thank you!

@Ulyev-ad commented on GitHub (Jun 16, 2020): Oh, I forgot to update. Yes, thank you!

GiteaMirror commented

2025-11-02 06:29:01 -06:00

@bobemoe commented on GitHub (Jul 14, 2020):

Which version is needed? I'm getting this error but no git updates:
git is already the newest version (1:2.11.0-3+deb9u7).

@bobemoe commented on GitHub (Jul 14, 2020): Which version is needed? I'm getting this error but no git updates: `git is already the newest version (1:2.11.0-3+deb9u7).`

GiteaMirror commented

2025-11-02 06:29:01 -06:00

@bobemoe commented on GitHub (Jul 14, 2020):

I'm using Debian 9. I've enabled the backports repo and managed to install Git 2.20.1 All is working now :)

@bobemoe commented on GitHub (Jul 14, 2020): I'm using Debian 9. I've enabled the backports repo and managed to install Git 2.20.1 All is working now :)

GiteaMirror commented

2025-11-02 06:29:01 -06:00

@zeripath commented on GitHub (Jul 28, 2020):

OK I'm reopening this as git name-rev --exclude is not available in git <2.13.

@zeripath commented on GitHub (Jul 28, 2020): OK I'm reopening this as `git name-rev --exclude` is not available in git <2.13.

GiteaMirror commented

2025-11-02 06:29:01 -06:00

@zeripath commented on GitHub (Jul 28, 2020):

Bug introduced by #11847

@zeripath commented on GitHub (Jul 28, 2020): Bug introduced by #11847

GiteaMirror referenced this issue

2025-11-02 16:12:22 -06:00