should I see a F18 branch?
Michael J Gruber
mjg at fedoraproject.org
Tue Sep 4 09:37:21 UTC 2012
Andrew Price venit, vidit, dixit 04.09.2012 01:43:
> On 03/09/12 23:31, Neal Becker wrote:
>> Ken Dreyer wrote:
>>> On Mon, Sep 3, 2012 at 4:01 PM, Neal Becker <ndbecker2 at gmail.com> wrote:
>>>> fedpkg pull
>>>> Already up-to-date.
>>>> git branch
>>>> * f17
>>> "git pull -a" will grab the f18 branch. Not sure why fedpkg doesn't do it.
>>> - Ken
>> $ git pull -a
>> Already up-to-date.
>> $ git branch
>> * f16
> Try 'git branch -a' or 'fedpkg switch-branch':
They do different things:
'git branch -a' shows all branches: local and remote (tracking)
'fedpkg switch-branch f18' creates a local branch f18 which has the
remote tracking branch remotes/origin/f18 as its upstream (unless it
exists already), and switches to it ('git checkout').
Doing a 'git fetch --all' to get the new remote branch would have showed
you that it ended up as a remote tracking branch in your repo.
'fedpkg pull' actually does more, it's fetch + merge or rebase!
> $ git branch -a
> * f18
> remotes/origin/HEAD -> origin/master
> $ fedpkg switch-branch
> * f18
More information about the devel