> ok, so there is no way to import GIT branches into LP, so we will be doing
> manual code review (sending patches to an internal list) for the next few
> weeks from the gnome-2-28 branch I've created in GIT.
>
> So, I'll approve your branch as soon as this other branch
> (https://code.edge.launchpad.net/~rodrigo-moya/couchdb-glib/no-revision-in-
> auth-header) gets accepted/merged. Just make sure your branch includes those 2
> simple fixes, push it, so that the new diff is shown, and, as I said, I'll
> approve it (and push it to GNOME master branch, if you can't do so) as soon as
> the other branch lands in GNOME GIT.
> ok, so there is no way to import GIT branches into LP, so we will be doing /code.edge. launchpad. net/~rodrigo- moya/couchdb- glib/no- revision- in-
> manual code review (sending patches to an internal list) for the next few
> weeks from the gnome-2-28 branch I've created in GIT.
>
> So, I'll approve your branch as soon as this other branch
> (https:/
> auth-header) gets accepted/merged. Just make sure your branch includes those 2
> simple fixes, push it, so that the new diff is shown, and, as I said, I'll
> approve it (and push it to GNOME master branch, if you can't do so) as soon as
> the other branch lands in GNOME GIT.
I've ported you fixes to my branch in rev. 117: http:// bazaar. launchpad. net/~kamstrup/ couchdb- glib/couchdb- glib-gtkdoc/ revision/ 117. I've have SSH keys for Gnome so I can merge it to master myself.