I tried Óscar's suggestion [below] to track the branch (local master)
from which I created another branch (foo) after creating foo at the
command line this way:
$ git branch -f --track foo master
Branch foo set up to track local branch master.
(-f forces creation even if foo exists)
Then I went into emacs magit mode and switched from master to foo with
the 'b' keystroke and saw these errors in my 'magit: pt' buffer:
Remote: .
Local: foo /htapps/pfarber.babel/pt/
Head: fcad4e9 * vendor/common-lib/lib: follow MULTIWORK_BOUNDARY changes
Unpulled commits:
fatal: ambiguous argument 'HEAD.../master': unknown revision or path not
in the working tree.
Use '--' to separate paths from revisions
Unpushed commits:
fatal: ambiguous argument './master..HEAD': unknown revision or path not
in the working tree.
Use '--' to separate paths from revisions
Has this kind of thing worked for others or did I create the foo branch
wrong from magit's perspective or is it a bug?
emacs 23.2
magit 0.8.1
- Phil Farber
On 12/15/2010 02:50 AM, Óscar Fuentes wrote:
Steinar Bang<[email protected]> writes:
[snip]
When a particular branch is checked out, I would like to see the commits
that haven't yet been merged back to the branch the current branch comes
from.
If you want that, use a tracking branch. Else a git branch does not know
the branch used for creating it.
