[PATCH 1 of 8] rust-hglib: import the latest version and update URLs

Yuya Nishihara yuya at tcha.org
Tue Apr 3 08:04:38 EDT 2018


On Mon, 2 Apr 2018 18:06:56 -0700, Gregory Szorc wrote:
> On Mon, Apr 2, 2018 at 5:53 PM, Kevin Bullock <
> kbullock+mercurial at ringworld.org> wrote:
> > > On Apr 1, 2018, at 13:53, Gregory Szorc <gregory.szorc at gmail.com> wrote:
> > > On Sun, Apr 1, 2018 at 4:14 AM, Yuya Nishihara <yuya at tcha.org> wrote:
> > > # HG changeset patch
> > > # User Kevin Bullock <kbullock at ringworld.org>
> > > # Date 1522477348 -32400
> > > #      Sat Mar 31 15:22:28 2018 +0900
> > > # Node ID 9e25c96124d51e11022b0ce64783f5f333ede7fb
> > > # Parent  2ed180117f7658d0cbf6a1ece20944465c55c947
> > > rust-hglib: import the latest version and update URLs
> > >
> > > Queued parts 1-3 because vendoring rust-hglib has been talked about and
> > agreed upon IIRC.
> >
> > Hmm, it has? Have we talked about vendoring other hglibs (c-hglib,
> > python-hglib)?
> >
> > I recall talking about consolidating them onto m-s.o. If we decide to
> > vendor them into the hg repo I think we should talk more about source
> > layout first, and start w/python-hglib.
> >
> > That being said, I'm excited to see interest around rust-hglib!
> >
> 
> I could be mistaken.
> 
> Obviously since I queued this, I have no problems taking the hglib clients
> into the main repo. I'm also fine putting rust-hglib on another repo on
> m-s.o/repo.

Dropped the patches from hg-committed for now.

Only reason I vendored rust-hglib was otherwise it would get complicated
to rewrite chg in Rust. But we can instead put chg into rust-hglib repository
(or a temporary fork of it.) That's probably less controversial and easier
to throw them away if the porting work turns out to be impractical.


More information about the Mercurial-devel mailing list