dpush does not update the working tree

Bug #1019987 reported by Alexander Belchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Triaged
Wishlist
Unassigned

Bug Description

After dpush all history is correct but the last change (from dpushed revision) appears in the log and in the working tree as uncommitted change:

C:\work\Documents\GitHub\test>git status
# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
#
# Changes to be committed:
# (use "git reset HEAD <file>..." to unstage)
#
# modified: .gitignore
#

C:\work\Documents\GitHub\test>git reset HEAD
Unstaged changes after reset:
M .gitignore

C:\work\Documents\GitHub\test>git status
# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
#
# Changes not staged for commit:
# (use "git add <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working directory)
#
# modified: .gitignore
#
no changes added to commit (use "git add" and/or "git commit -a")

C:\work\Documents\GitHub\test>git reset --hard HEAD
HEAD is now at 21bc0d8 add newline to .gitignore

C:\work\Documents\GitHub\test>git status
# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
#
nothing to commit (working directory clean)

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

This is known behaviour - dpush does not update the working tree at the moment.

Changed in bzr-git:
status: New → Triaged
importance: Undecided → Wishlist
summary: - local dpush from bzr to git tree doesn't update git tree properly
+ dpush does not update the working tree
affects: bzr-git → bzr
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.