And then the merge request, is that from jeff/kicad:jeffDRC to jeff/kicad:master, or is there some way to do a merge request from jeff/kicad:jeffDRC to kicad/code/kicad:master?
> On 26 Apr 2020, at 14:50, Ian McInerney <ian.s.mciner...@ieee.org> wrote: > > Jeff, > > From the main repository page, simply click on "Fork" at the top of the page. > Then you create it inside your Personal namespace. Once you do that, the fork > can just become a new remote in your git repository. > > https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork > > <https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork> > > -Ian > > On Sun, Apr 26, 2020 at 2:48 PM Jeff Young <j...@rokeby.ie > <mailto:j...@rokeby.ie>> wrote: > I don’t have a personal repo. Is it (reasonably) obvious how to create one? > > > On 26 Apr 2020, at 14:32, Wayne Stambaugh <stambau...@gmail.com > > <mailto:stambau...@gmail.com>> wrote: > > > > Hi Jeff, > > > > Would you please move your working branch from the main repo to your > > personal repo and create a merge request? This will make it much easier > > to test and avoid poluting the main repo with developers personal > > working branches. > > > > Thanks, > > > > Wayne > > > > On 4/26/20 8:27 AM, Jeff Young wrote: > >> I have added code to many DRC errors which shows the minimum clearance, > >> its source, and the actual clearance. > >> > >> The old DRC code was pretty heavily optimised around the idea of only > >> needing to know if the clearance was violated (and not by how much), so > >> a lot of it has been re-written. For this reason the new code is > >> currently in a branch (jeffDRC). > >> > >> I’d appreciate some testing on it if anyone gets a chance. (More on the > >> DRC errors themselves than the new reporting.) > >> > >> Cheers, > >> Jeff. > >> > >> PS: feel free to report issues here in email, or > >> in https://gitlab.com/kicad/code/kicad/-/issues/2313 > >> <https://gitlab.com/kicad/code/kicad/-/issues/2313>. > >> > >> _______________________________________________ > >> Mailing list: https://launchpad.net/~kicad-developers > >> <https://launchpad.net/~kicad-developers> > >> Post to : kicad-developers@lists.launchpad.net > >> <mailto:kicad-developers@lists.launchpad.net> > >> Unsubscribe : https://launchpad.net/~kicad-developers > >> <https://launchpad.net/~kicad-developers> > >> More help : https://help.launchpad.net/ListHelp > >> <https://help.launchpad.net/ListHelp> > >> > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~kicad-developers > > <https://launchpad.net/~kicad-developers> > > Post to : kicad-developers@lists.launchpad.net > > <mailto:kicad-developers@lists.launchpad.net> > > Unsubscribe : https://launchpad.net/~kicad-developers > > <https://launchpad.net/~kicad-developers> > > More help : https://help.launchpad.net/ListHelp > > <https://help.launchpad.net/ListHelp> > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > <https://launchpad.net/~kicad-developers> > Post to : kicad-developers@lists.launchpad.net > <mailto:kicad-developers@lists.launchpad.net> > Unsubscribe : https://launchpad.net/~kicad-developers > <https://launchpad.net/~kicad-developers> > More help : https://help.launchpad.net/ListHelp > <https://help.launchpad.net/ListHelp>
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
