Plea for mercurial_keyring to be pulled into tree

Matt Mackall mpm at selenic.com
Wed Nov 23 11:57:58 CST 2011


On Mon, 2011-11-21 at 17:48 +0100, Markus Zapke-Gründemann wrote:
> Matt Mackall schrieb:
> > On Mon, 2011-11-21 at 16:10 +0100, Markus Zapke-Gründemann wrote:
> >> Markus Zapke-Gründemann schrieb:
> >>> Matt Mackall schrieb:
> >>>> On Thu, 2011-11-17 at 13:42 +0100, Markus Zapke-Gründemann wrote:
> >>>>> Matt Mackall schrieb:
> >>>>>> On Wed, 2011-10-19 at 14:41 +0200, Markus Zapke-Gründemann wrote:
> >>>>>>> Hi Marcin,
> >>>>>>>
> >>>>>>> what's the status of the inclusion of mercurial keyring with Mercurial? Do you
> >>>>>>> need any help to prepare this?
> >>>>>> It'll have to wait for after Nov 1st now.
> >>>>> Matt, any news here?
> >>>> Yes! It's officially after Nov 1st, so it no longer needs to wait.
> >>> It looks Marcin has not enough time to drive the inclusion of mercurial keyring
> >>> into the core. I asked Steve but he is also too busy to help here. So I would
> >>> propose that I will create a patch which can be discussed here when it's done.
> >> Matt, I'm sorry I have to bother you again. But before I start to work on
> >> including mercurial keyring into the core it's important for me to know if you
> >> would accept a patch by me in general, even if I'm not the maintainer of
> >> mercurial keyring. Otherwise it wouldn't make much sense for me to invest time
> >> in a patch which wouldn't be accepted by default.
> > 
> > The things I generally care about when pulling in something like this:
> > 
> > - approval from author
> > - someone committed to ongoing maintenance
> > - license compatibility
> > - conformance to our style and coding guidelines
> > - general compatibility with Mercurial design philosophy
> > 
> > That second one is the one that worries me most with keyring at the
> > moment. 
> I would take care of the maintenance.

Great, please proceed.

-- 
Mathematics is the supreme nostalgia of our time.




More information about the Mercurial-devel mailing list