Closed
Bug 928477
Opened 11 years ago
Closed 11 years ago
bzexport should default to '.' and not 'tip' for exported revision
Categories
(Developer Services :: Mercurial: bzexport, defect)
Developer Services
Mercurial: bzexport
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gps, Assigned: sfink)
Details
Attachments
(1 file)
2.23 KB,
patch
|
emorley
:
review+
|
Details | Diff | Splinter Review |
bzexport currently defaults to 'tip' when choosing the revision to export. This fails to work with bookmark or branch workflows. I'm in the process of switching my workflow to branches. My local repo contains a bunch of changesets that never get exported to published repositories. I frequently commit new changes on my bookmarks then pull new changesets from the canonical repos. This means that 'tip' is typically inbound's head. bzexport attempts to export 'tip' and not my active head. I think this is wrong. I believe bzexport should export '.' by default instead. Fortunately, you can work around this by running |hg bzexport .|.
Assignee | ||
Comment 1•11 years ago
|
||
Yeah, using 'tip' for just about anything is Wrong.
Attachment #819138 -
Flags: review?(emorley)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → sphink
Status: NEW → ASSIGNED
Comment 2•11 years ago
|
||
Comment on attachment 819138 [details] [diff] [review] Default to "." instead of "tip" Review of attachment 819138 [details] [diff] [review]: ----------------------------------------------------------------- lgtm :-)
Attachment #819138 -
Flags: review?(emorley) → review+
Comment 3•11 years ago
|
||
This is probably an artifact of me not understanding the difference at the time I wrote bzexport.
Assignee | ||
Comment 4•11 years ago
|
||
I've never actually used bzexport with anything but mq patches, so I'm not entirely clear what it does for other commits.
Assignee | ||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Other Applications → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•