gawkworkflow: Remotes
1
1 2.4.3 A Closer Look at Branch Naming
1 ------------------------------------
1
1 Earlier, we said that Git maintains copies of the branches in the
1 upstream repo, as well as manages your local branches. You can see all
1 these branches with 'git branch -a':
1
1 $ git branch -a
1 -| gawk-4.1-stable
1 -| * master
1 -| remotes/origin/HEAD -> origin/master
1 -| remotes/origin/dead-branches/async-events
1 -| ...
1 -| remotes/origin/feature/api-mpfr
1 -| remotes/origin/feature/array-iface
1 -| remotes/origin/feature/fix-comments
1 -| ...
1
1 You'll note that what we've referred to as 'origin/' branches appear
1 in the output with an additional prefix: 'remotes/'. Up to this point,
1 we've treated Git as if it allowed only a singled upstream repository.
1 But in fact, you can configure it to use more than one. All the known
1 upstream repositories are grouped under the 'remotes/' prefix, with
1 'remotes/origin' being the one from which you initially cloned your
1 local repository.
1
1 The ability to work with multiple upstream repositories is an
1 advanced one; 'gawk' development does not make use of it. The intent of
1 this node is to explain the output from 'git branch -a', nothing more.
1