Skip to contentSkip to conversation

Best way to specify all local branches and all remote branches.

DISCUSSION Paul Gardiner 3 participants 6 messages Jun 15, 2016

lore
Share & tools
lore
#0 lore raw

New to git, and often finding it hard to specify the correct refs for a command. Here's an example where I was converting all the files in all the commits from unix line endings to DOS line endings. You can see I've ended up using cd and ls. I'm sure there must be a better way.

$ cd /home/public/tmp/git/
$ yes |rm -r vdos32
$ git clone /export/git/vdos32.git vdos32
$ cd vdos32/
$ for f in `(cd /export/git/vdos32.git/refs/heads; ls)|sed -e
   '/master/d' -e '/origin/d'`; do git fetch origin $f:$f; done
$ git-filter-branch --tag-name-filter cat --tree-filter 'find . -type f
   ! -name \*.gif ! -name \*.ico|xargs unix2dos -q' `(cd
   .git/refs/heads;ls)`

With git-filter-branch, I'm surprised I can't use --all. The docs suggest that A --not B is permitted. I've also seen refs/heads/* used in the docs but never managed to get it to work. Most greatful for any advice.

P.

#1 lore raw
Quoted 5 lines · Paul Gardiner

New to git, and often finding it hard to specify the correct refs for a command. Here's an example where I was converting all the files in all the commits from unix line endings to DOS line endings. You can see I've ended up using cd and ls. I'm sure there must be a better way.

git-for-each-ref, git-show-ref, git-ls-remote / git-peek-remote.

Quoted 9 lines
$ cd /home/public/tmp/git/
$ yes |rm -r vdos32
$ git clone /export/git/vdos32.git vdos32
$ cd vdos32/
$ for f in `(cd /export/git/vdos32.git/refs/heads; ls)|sed -e
    '/master/d' -e '/origin/d'`; do git fetch origin $f:$f; done
$ git-filter-branch --tag-name-filter cat --tree-filter 'find . -type f
    ! -name \*.gif ! -name \*.ico|xargs unix2dos -q' `(cd
    .git/refs/heads;ls)`

If you want to fetch all branches, you can specify globbing refspec; of course if you use separate remotes layout, or mirror layout.

If you want to pass all branches to git command, usually --all would be enough (sometimes --heads).

Quoted 1 line

With git-filter-branch, I'm surprised I can't use --all.

git-filter-branch is about single branch; I'm not sure if it should support --all.

Signature · 3 lines
Jakub Narebski
Poland
ShadeHawk on #git
#2 lore raw
Quoted 9 lines · Jakub Narebski
Quoted 5 lines · Paul Gardiner

New to git, and often finding it hard to specify the correct refs for a command. Here's an example where I was converting all the files in all the commits from unix line endings to DOS line endings. You can see I've ended up using cd and ls. I'm sure there must be a better way.

git-for-each-ref, git-show-ref, git-ls-remote / git-peek-remote.

Ah right, those look hellishly useful, thanks.

Quoted 10 lines
Quoted 9 lines
$ cd /home/public/tmp/git/
$ yes |rm -r vdos32
$ git clone /export/git/vdos32.git vdos32
$ cd vdos32/
$ for f in `(cd /export/git/vdos32.git/refs/heads; ls)|sed -e
    '/master/d' -e '/origin/d'`; do git fetch origin $f:$f; done
$ git-filter-branch --tag-name-filter cat --tree-filter 'find . -type f
    ! -name \*.gif ! -name \*.ico|xargs unix2dos -q' `(cd
    .git/refs/heads;ls)`
Quoted 2 lines

If you want to fetch all branches, you can specify globbing refspec; of course if you use separate remotes layout, or mirror layout.

I think I tried that with my line 5 above. I tried refs/heads/*:refs/heads/* as the ref spec. Should something like that work?

Quoted 7 lines

If you want to pass all branches to git command, usually --all would be enough (sometimes --heads).

Quoted 1 line

With git-filter-branch, I'm surprised I can't use --all.

git-filter-branch is about single branch; I'm not sure if it should support --all.

It seems to work with multiple branches, and I think it's important that it does, because as far as I can tell, that's the only way to filter a whole repository without visiting some commits more than once. Certainly my command, using cd/ls, worked and visited each commit exactly once.

Cheers,
Paul.

#4 lore raw
Quoted 11 lines · Johannes Schindelin

Hi,

Quoted 1 line · Jakub Narebski

git-filter-branch is about single branch;

No.

Quoted 1 line

I'm not sure if it should support --all.

It does.

Yep, it does. I'd forgotten how to drive the shell. It works if I put -- --all.

Turns out that isn't what I want though. I want just the local branches. Still can't find a way to do it other than my cd/ls thing.

#5 lore raw
Quoted 5 lines · Paul Gardiner
Quoted 4 lines · Johannes Schindelin
Quoted 1 line · Jakub Narebski

git-filter-branch [...] should support --all.

Quoted 8 lines
Quoted 1 line

It does.

Yep, it does. I'd forgotten how to drive the shell. It works if I put -- --all.

Turns out that isn't what I want though. I want just the local branches. Still can't find a way to do it other than my cd/ls thing.

I wrote: git-for-each-ref(1). See documentation, please.

  $(git for-each-ref --shell --format="%(refname)" "refs/heads/*")
Signature · 3 lines
Jakub Narebski
Poland
ShadeHawk on #git