On 01/25/2016 01:58 PM, Mike Hommey wrote:
On Mon, Jan 25, 2016 at 11:23:59AM -0800, Steve Fink wrote:
- will it be possible to still be using hg patch queues?
A valid question, though I'd not that the mq-less workflow is actually
pretty good these days. mq is still easier/nicer for some things, but doing
without mq is nicer in other ways, and the future leads away from mq.
On the other hand, there still isn't a great way to figure out the mq-less
workflow. I remember a pretty good writeup from someone, and I intend to
write up my own. But there isn't anything that's easily discoverable.
Whether or not mq is deprecated, it still uses changesets that can be
pushed. And with a non publishing remote repository, it should still be
able to qpop without having to fool around with the draft state.
For the first (force) push, sure. But given mq's love of rewriting
history, I assume it will not maintain any correspondence between
versions of a patch (either via obsolescence markers, or gps's magic
metadata field, or whatever). So if you push an updated patch, I
wouldn't expect it to be able to figure out that it's an update of an
earlier commit? Unless it's doing some heuristic matching on comments or
something.
It just got one of my patches wrong, though, so maybe it *is* doing
something fancy. :-)
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
