=== sem2peie- is now known as sem2peie
=== sem2peie- is now known as sem2peie
=== lucas_ is now known as Guest55863
=== ginggs_ is now known as ginggs
[19:51] <tilgovi> I'm trying to submit my first patch, which would be a tiny (one character!) fix to a control file to correct a typo in a recommended dependency. The code is in git, I have cloned the repo using `git ubuntu clone`, I have been reading what I can find on the wiki for a few hours, but I'm still kinda lost. Can anyone help me out?
[19:52] <tilgovi> I'm trying to figure out if there's more to this than what my git experience tells me. My guess is to make a branch called X.Y.Z-NubuntuM and just commit a change to the control file and add a changelog entry. Then what?
[19:54] <tilgovi> Or do I make a branch named after the change I'm making, and update only the control file, then let the maintainer merge it and update the changelog? Must I file a bug first?
[21:15] <rbasak> tilgovi: we haven't yet defined a specific process for contributors to use git-ubuntu to propose changes to land in Ubuntu, although the actual pieces are generally in place already. So yes, you can submit a merge proposal against a git-ubuntu branch.
[21:16] <rbasak> tilgovi: assuming the change is appropriate for Ubuntu to adopt directly, you can add commits as you wish to change debian/control and add an entry to debian/changelog, push that branch, and then submit a Launchpad merge proposal against it.
[21:37] <rbasak> tilgovi: if you do, please let us know here, because we don't have a process for looking at merge proposals automatically yet either