1 (This is a draft. The method here won't actually work yet, because
2 neither git-new-workdir nor merge-changelog are in the Emacs
5 Setting up and using git for normal, simple bugfixing
6 =====================================================
8 If you haven't configured git before you should first do:
10 git config --global user.name "Frank Chu"
11 git config --global user.email "fchu@example.com"
16 Then we want to clone the repository. We normally want to have both
17 the current trunk and the emacs-24 branch.
21 git clone <membername>@git.sv.gnu.org:/srv/git/emacs.git
23 ./trunk/admin/git-new-workdir trunk emacs-24
27 You now have both branches conveniently accessible, and you can do
28 "git pull" in them once in a while to keep updated.
34 You edit the files in either branch, `M-x vc-dir', and check in your
35 changes. Then you need to push the data to the main repository. This
36 will usually fail, since somebody else has pushed other changes in the
37 meantime. To fix this, say
41 which will update your repository, and then re-apply your changes on
47 Backporting to emacs-24
48 =======================
50 If you have applied a fix to the trunk, but then decide that it should
51 be applied to the emacs-24 branch, too, then
56 and find the commit you're looking for. Then find the commit ID,
59 commit 958b768a6534ae6e77a8547a56fc31b46b63710b
62 git cherry-pick -xe 958b768a6534ae6e77a8547a56fc31b46b63710b
64 and add "Backport:" to the commit string. Then
69 Merging emacs-24 to trunk
70 =========================
72 This has yet to be written.
75 Warnings about X11 forwarding
76 =============================
78 If you get warnings like
80 Warning: No xauth data; using fake authentication data for X11 forwarding.
81 X11 forwarding request failed on channel 0
83 when pulling or pushing data, add the following to the start of