Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--all does not what the help says #555

Closed
matthiasbeyer opened this issue Dec 7, 2016 · 3 comments
Closed

--all does not what the help says #555

matthiasbeyer opened this issue Dec 7, 2016 · 3 comments

Comments

@matthiasbeyer
Copy link

If you call tig --all it does: Display all branches: (from man tig). This is not what it does:

I have refs in .git/refs/foo/ which are also shown - technically, these are also branches, but not semantically. Semantically, only things in .git/refs/{remotes,heads,tags} are branches.

After all, I'm not entirely happy with the semantics here. I would like to propose the following changes:

  • Keep the --all flag and its current behaviour, change the documentation accordingly
  • Introduce --all-branches or something like that to only show (semantical) branches
  • Introduce another flag to show all .git/refs/* but not the branches from the {heads,remotes,tags}.

What do you think?

jonas added a commit that referenced this issue Dec 9, 2016
@jonas
Copy link
Owner

jonas commented Dec 9, 2016

I've updated the documentation using the wording from git-log(1). Hopefully this makes it more clear what tig --all does.

You can pass any git-log flag you want to Tig and it should select and filter as if you called git-log. If you only want branches something like this should work:

tig --branches

Given that git-log already has an extensive number of flags I'd prefer not to add any custom flags to Tig itself.

@matthiasbeyer
Copy link
Author

Hm, this does not work for me, unfortunately. I mean, it also lists refs from refs/remotes/upstream, even when I pass --exclude=refs/remotes/upstream/*

@jonas jonas closed this as completed in 2c2c279 Feb 6, 2017
@jonas
Copy link
Owner

jonas commented Feb 6, 2017

I've pushed a fix for using --exclude=refs/remotes/upstream/* together with --all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants