Add a New Comment Rich Markup
I guess this should be done in function rename_in_db(), to make sure we cover all present and future situations.
If you force-push a patch that does not apply cleanly, quilt tells you it needs to be refreshed, and creates a marker to remember this under .pc/. If you rename the patch before refreshing it, quilt will forget about this. So it will let you continue even if the patch was not refreshed, and it will never delete the marker. We need to rename the marker when a patch which needs to be refreshed is renamed. Same is probably needed for the fork command as well, as it's essentially a rename with a backup. The test suite should cover this scenario.
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Copyright © 2023 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.12