Re: Change .page, see result
Hannie Dumoleyn <[email protected]>
| Newsgroups | gmane.comp.gnome.documentation |
|---|---|
| Message-ID | <[email protected]> |
Hi Germán, Wow, these sure are encouraging words. I will answer between the lines: Op 06-12-17 om 13:27 schreef Germán Poo-Caamaño: > Hi Hannie, > > I am very sorry that my pointers turned out to be more complex than I > anticipated. I believe I was not clear enough on what I meant. > > Let us step back a bit and be sure we are on the same page (no pun > intended with respect to the subject of this thread). > > My understanding is that you are already using git, and you have a > branch with your changes in the documentation. Therefore, you want to > know how to submit your changes in bugzilla. That's right. I use git (clone, add, commit, push, and checkout) to upload translations (.po files) to the server. But now I want to start contributing as a reviewer/author for gnome-user-docs and gnome-getting-started-docs as well. I have changed gs-use-system-search.page and I have checked the changes on my pc using Yelp. From what Ekaterina wrote, I understand that I should not push my local branch, gnome-getting-started-docs, to git.gnome. Instead, I should send a patch to Bugzilla. I just checked Gunnar's notes, thanks Gunnar!, and I will try the last steps (git add *, git commit and git format-patch HEAD~). If it works, it will make me very happy indeed :) If not, I will ask further questions on this list or on irc. > Considering that, I meant to say that you should consider only the link > to submit a patch, not the previous steps about building a project > and/or installing Builder or jhbuild. The reason why I looked at the previous steps is because I could not create a patch (step 4). In the example I saw nautilus(~/jhbuild/checkout) master, so my conclusion was I should install jhbuild first. Hannie _______________________________________________ gnome-doc-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-doc-list