"Patch Management" descriptions in conflict

[Dave S]

I am one of those that never got around to trying MQ, so I can't talke to
how desirable it is.   I've had pretty simple use-cases, mostly linear
development with the occasional rollback when I mess up a commit.  And
mostly single user, although some of those repositories may stage code that
I'll check into the corporate SVN.

My impression (mainly from this list) is that MQ' s popularity peaked a
while ago, and that some of that group is exploring the evolve tools.  And
don't Tortoise HG users also have access to a flavor of "shelve" that may
be a reasonable alternative to MQ for simple situations?  And from the
HG-Dev list, I get the impression that the MQ code is pretty stable,
although it would be changing more if evolve hadn't shown up.

There used to be a lot more MQ questions around here, even just a year
IIRC.  Everybody that's using has it figured out now, I guess.

/dps





On Thu, Jan 30, 2014 at 6:24 AM, BOGGESS Rod CORE <Rod.Boggess at tenova.com>wrote:

>
>
>
>
> *From:* srasku at gmail.com [mailto:srasku at gmail.com] *On Behalf Of *Stephen
> Rasku
> *Sent:* Wednesday, January 29, 2014 3:33 PM
> *To:* BOGGESS Rod CORE
> *Cc:* mercurial at selenic.com
>
> *Subject:* Re: "Patch Management" descriptions in conflict
>
>
>
> On Wed, Jan 29, 2014 at 11:37 AM, BOGGESS Rod CORE <Rod.Boggess at tenova.com>
> wrote:
>
> ...
>
>
> By Bryan's own admission, the relevance of MQ in the book is overrated
>
> with respect to the current state of things....
> GGhh
>
> I'm wondering what that means, "relevance...overrated...". I do agree that MQ,
> being a more advanced use-case, should be addressed in an Appendix,
> although it would be a tough call, and I think even the two paragraphs
> could be expanded to do it justice. Not enough information exists (for my
> tastes) on sub-repos, which should probably have equal footing to MQ.
>
> But this statement leaves me with the impression that few are using MQ,
> and I wonder if there's any actual numbers on its popularity amongst users.
>
> I've used MQ in the patch and I continue to do so.  I like the fact that I
> can go back an modify patches and that I can fold multiple patches into a
> single commit when I'm ready.
>
> ...Stephen
>
>
>
>  Well, if you and I are the only two users of MQ on this list, and this
> group is representative, I guess I have my answer. I admit, though, that
> I'm surprised.
>
>
>
> I do field deployment of customized automation software. It's an excellent
> tool for managing temporary software (especially the guards), it's great
> for testing out software modifications or patches prior to committing, and
> we've even used it to maintain a Visual Studio 2005 application using
> Visual Studio 2008.  (Upgrade to 2008, and save that as a patch. Make your
> changes, save those as a patch. Pop both off, swap order, and finish the
> changes you made. Then when a 2005 user pulls the changes down, he doesn't
> see the upgrade changes, since they remain in the patch you didn't finish.)
>
>
>
>
>
>
> *[image: Tenova]*
>
> <http://www.tenova.com>
>
> <http://http://www.tenova.com>
>
>
> *Tenova: advanced technologies for the metals and mining industries *Visit
> our website at www.tenova.com <http://www.tenovagroup.com/>
> ------------------------------
>
> Confidentiality Notice : This message, together with its attachments,
> contains strictly confidential information and is intended only for the
> addressee identified above, who is the sole party authorized to use and
> copy it and, assuming any related liability , to forward it to
> others. Anyone receiving this message by mistake or reading it without
> authorization is hereby notified that storage, reproduction, disclosure
> or distribution of the message to persons other than the addressee is
> strictly forbidden. They are asked to return the message immediately to the
> sender and to erase the original message received.
> Thank you.
>
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
>


-- 
test signature -- please apply at front gate on Tuesdays only.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140130/553a6b1b/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image4b0562.JPG
Type: image/jpeg
Size: 16909 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140130/553a6b1b/attachment-0002.jpe>