Closed
Bug 1720931
Opened 3 years ago
Closed 3 years ago
moz-phab 1.0.0rc1 is leaking changes between revisions in stack
Categories
(Conduit :: moz-phab, defect, P2)
Conduit
moz-phab
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mhentges, Assigned: zeid)
Details
(Keywords: conduit-triaged)
Attachments
(3 files)
Some changes from my 2nd revision are appearing as part of my 1st revision on Phabricator.
See the first revision on Phabricator where all of ensure_python_modern()
was removed, but it was just supposed to partly remove the function (like this).
Other notes:
- This doesn't happen with
0.1.99
. - This doesn't happen if I individually submit the patches with
moz-phab -s
.
Reporter | ||
Comment 1•3 years ago
•
|
||
I've simplified the reproduce criteria a bit:
- The two revisions now only remove two functions - one per patch, each adjacent to each other
- Revision 1 removes
is_python_modern()
: phabricator shows that it remove both functions - Revision 2 removes
ensure_python_modern()
: phabricator shows this correctly
- Revision 1 removes
Local hg show work
looks like:
@ 18304b2 Bug 1720925: [test] Move platform-specific Python upgrade instructions
o 33c7621 Bug 1720925: [test] Remove Python 2 warning from bootstrap
o 160071a (central) Bug 1720633 - Remove old "network.http.spdy.bug1563538" pref checks. r=necko-reviewers,kershaw
Reporter | ||
Updated•3 years ago
|
Summary: moz-phab 1.0.0rc1 is leaking changes between changes in stack → moz-phab 1.0.0rc1 is leaking changes between revisions in stack
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
Some mercurial commands still rely on the repo being checked out in
order to generate the correct hunks for diffs when running the submit
command. This is a temporary fix that will result in the right
hunks/diffs being generated, until the rest of the code is refactored.
Assignee | ||
Comment 3•3 years ago
|
||
Fix will be release with 1.0.0rc2
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•