Hi, Christian PERRIER <bubulle@debian.org> (2015-05-02): > Quoting Mathieu Trudel-Lapierre (mathieu.tl@gmail.com): > > Hi everyone, > > > > I'm Mathieu, from Montreal. I've just subscribed to debian-boot@, > > but I've already been idling in #debian-boot for a while, I was one > > of the drivers of the Montreal bid for Debconf16, and I've been > > taking on d-i work for Ubuntu. I've already been bugging cjwatson > > every once in a while to review changes or merge git branches for > > things like grub, but I realise I should reach out more :) > > Yes! Oui ! ;-) \o/ Welcome on board! > > What would be the preferred method for this? My initial focus will > > be patches for multipath support that don't appear to have > > associated BTS bugs. Is it fine to push to git for code to be > > reviewed (in my own people/cyphermox-guest/xyz branch), or should I > > file bugs and attach patches? > > Well, let's get Kibi's stance on this, but I think the best should be > that you directly commit things in git, just like Colin has been doing > for years. > > If you do so, it's likely that the "bubulle manual autobuilder" will > catch your changes and upload them quite soon so that they get tested > (well, assuming people really testing daily images and unstable > installs).... If you're convinced your changes are OK and can go to master, push them there. If you want them to be reviewed/commented upon/refined, feel free to push them into a branch with a descriptive name, and tell us about it. :) Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature