On Mon, Aug 28, 2017 at 03:47:34PM -0700, Danek Duvall wrote: > Durham Goode wrote: > > On 8/25/17 11:55 AM, Danek Duvall wrote: > > > Along similar lines, I've also wanted the ability to push and pull secret > > > changesets between (non-publishing) repositories, but only when > > > specificied > > > by name like this. Seems like there could be some shared mechanism there, > > > if it's not just me. > > > > We don't really use secret commits here. Instead, we've overriden the push > > behavior to require the user to specify what they want to push and where > > they want to push to (hg push -r mybookmark --to theirbookmark). So we > > haven't really needed secret as a mechanism for controlling exchange. > > Sure, though of course not everyone works at Facebook, and those that do, > might work in other contexts, too. It's certainly a workflow I've found > useful in the past. I'm certainly not asking for implementation here, just > a confirmation that there's enough alignment here that implementing that at > some point would be easier because of your work.
I also want this, but haven't had the time to figure out how to handle exchanging secret revisions. It's not a common thing, but I think I hit places where it'd be useful at least once a quarter, and if I could do it I'd probably hit those cases more often... > > Thanks, > Danek > _______________________________________________ > Mercurial-devel mailing list > Mercurial-devel@mercurial-scm.org > https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
