Hi Kendy, thanks a lot for the explanation on how to get change ids into older commits. David indicated something in this direction. I'll try to commit the last missing patch myself. Anyway I'm glad David reviewed the build related stuff.
Cheers, P. Von meinem iPhone gesendet Am 11.09.2012 um 12:40 schrieb Jan Holesovsky <ke...@suse.cz>: > Hi Peter, > > Peter Jentsch píše v Ne 09. 09. 2012 v 23:16 +0200: > >> I'm attaching a series of patches that I can't seem to get into gerrit >> (presumably because the first commits precede the switch to gerrit and >> thus don't carry a change-id). I'd gladly submit them to gerrit if sb >> tells me how to produce change-ids for the older commits. > > IIRC you have the push access, so you do not have to use gerrit to get > your changes in. If you haven't done that yet, you only need to setup > your gerrit credentials (including sending a mail to Norbert/Bjoern), > and do > > ./g --set-push-user <your_gerrit_username> > > Then you can push as before. Additionally, the sending to the mailing > list still works, and will always work :-) > > Regarding the generation of the change-id, it is enough to do 'git > rebase -i origin/master', and mark all the commit messages that are > missing the change-id as "reword"; the git commit hook will generate the > change-id after you just save the commit as it was. > > All the best, > Kendy > > _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
