[Bug 4007] New: pull --update doesn't update to active bookmark
mercurial-bugs at selenic.com
mercurial-bugs at selenic.com
Thu Aug 1 02:58:09 UTC 2013
http://bz.selenic.com/show_bug.cgi?id=4007
Priority: normal
Bug ID: 4007
CC: mercurial-devel at selenic.com
Assignee: bugzilla at selenic.com
Summary: pull --update doesn't update to active bookmark
Severity: bug
Classification: Unclassified
OS: Mac OS
Reporter: kbullock+mercurial at ringworld.org
Hardware: Macintosh
Status: UNCONFIRMED
Version: 2.6.3
Component: Mercurial
Product: Mercurial
When pulling from a repo that moves the active bookmark to a non-head, `hg pull
--update` behaves differently than `hg pull; hg update`: it will update to the
head and de-activate the active bookmark.
$ hg log -G
@ changeset: 0:f360df9189f7
bookmark: @
tag: tip
user: Kevin Bullock <kbullock at ringworld.org>
date: Wed Jul 31 21:52:41 2013 -0500
summary: 0
$ hg clone . ../b
updating to bookmark @
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ echo b>>a
$ hg ci -m1
$ hg bo -i
$ echo c>>a
$ hg ci -m2
$ hg log -G
@ changeset: 2:abf97d76172a
| tag: tip
| user: Kevin Bullock <kbullock at ringworld.org>
| date: Wed Jul 31 21:54:30 2013 -0500
| summary: 2
|
o changeset: 1:4bcecc64d03a
| bookmark: @
| user: Kevin Bullock <kbullock at ringworld.org>
| date: Wed Jul 31 21:54:12 2013 -0500
| summary: 1
|
o changeset: 0:f360df9189f7
user: Kevin Bullock <kbullock at ringworld.org>
date: Wed Jul 31 21:52:41 2013 -0500
summary: 0
$ cd ../b
$ hg pull --update
pulling from /Users/kbullock/Source/Explorations/hg/pull-update-bookmark/a
searching for changes
adding changesets
adding manifests
adding file changes
added 2 changesets with 2 changes to 1 files
updating bookmark @
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg sum
parent: 2:abf97d76172a tip
2
branch: default
commit: (clean)
update: (current)
$ hg bo
* @ 1:4bcecc64d03a
$ hg update
updating to active bookmark @
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list