Re: REST-API: Merging/Rebasing with Mercurial?

Mathias Behrle <[email protected]> Fri, 18 Jan 2019 18:06:12 +0100

Newsgroups	gmane.comp.bug-tracking.roundup.devel
Organization	MBSolutions
Message-ID	<[email protected]>

* Ralf Schlatterbeck: " [Roundup-devel] REST-API: Merging/Rebasing with
  Mercurial?" (Fri, 18 Jan 2019 16:06:39 +0100):

> As you may know we had a Google Summer of Code (GSoC) Project in 2015
> that added a REST-API to roundup. I'd like to integrate this code.
> The original announcement is at
> https://sourceforge.net/p/roundup/mailman/message/34436352/
> and there is also an issue in the tracker:
> https://issues.roundup-tracker.org/issue2550734

Interesting!

> If our version-control system was git I'd add a new remote to my
> checkout of roundup, pull the repo above into a new local branch, rebase
> to the current master and start fixing python3 compatibility issues and
> adding documentation.
> 
> Can someone outline how to achieve this with mercurial?

Basically it works like that:

hg pull -f <other_repos>
hg checkout <own_branch_to_update>
hg merge <foreign_branch_to_merge>
hg commit

I am meanwhile running roundup with some fixes under Python3 and I am wondering
which is considered the best way to publish those fixes. Should I publish the
repository elsewhere for inspection and discuss the individual issues on the
list? Should I post individual patches to the list? Please advise.

Thanks

Mathias



-- 

    Mathias Behrle
    MBSolutions
    Gilgenmatten 10 A
    D-79114 Freiburg

    Tel: +49(761)471023
    Fax: +49(761)4770816
    http://www.m9s.biz
    UStIdNr: DE 142009020
    PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
    AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6

_______________________________________________
Roundup-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-devel

signature.asc (application/pgp-signature, 867 B)