Commit | Line | Data |
0549aefb |
1 | =for comment |
2 | Consistent formatting of this file is achieved with: |
3 | perl ./Porting/podtidy pod/perlrepository.pod |
4 | |
d7dd28b6 |
5 | =head1 NAME |
6 | |
7 | perlrepository - Using the Perl source repository |
8 | |
9 | =head1 SYNOPSIS |
10 | |
dc3c3040 |
11 | All of Perl's source code is kept centrally in a Git repository at |
c26da522 |
12 | I<perl5.git.perl.org>. The repository contains many Perl revisions from |
13 | Perl 1 onwards and all the revisions from Perforce, the version control |
14 | system we were using previously. This repository is accessible in |
15 | different ways. |
d7dd28b6 |
16 | |
17 | The full repository takes up about 80MB of disk space. A check out of |
d9847473 |
18 | the blead branch (that is, the master branch, which contains bleadperl, |
19 | the development version of perl 5) takes up about 160MB of disk space |
20 | (including the repository). A build of bleadperl takes up about 200MB |
21 | (including the repository and the check out). |
d7dd28b6 |
22 | |
23 | =head1 GETTING ACCESS TO THE REPOSITORY |
24 | |
25 | =head2 READ ACCESS VIA THE WEB |
26 | |
dc3c3040 |
27 | You may access the repository over the web. This allows you to browse |
28 | the tree, see recent commits, subscribe to RSS feeds for the changes, |
29 | search for particular commits and more. You may access it at: |
d7dd28b6 |
30 | |
31 | http://perl5.git.perl.org/perl.git |
32 | |
dc3c3040 |
33 | A mirror of the repository is found at: |
34 | |
35 | http://github.com/github/perl |
36 | |
d7dd28b6 |
37 | =head2 READ ACCESS VIA GIT |
38 | |
39 | You will need a copy of Git for your computer. You can fetch a copy of |
40 | the repository using the Git protocol (which uses port 9418): |
41 | |
3b8a5fb0 |
42 | git clone git://perl5.git.perl.org/perl.git perl-git |
d7dd28b6 |
43 | |
f755e97d |
44 | This clones the repository and makes a local copy in the F<perl-git> |
d7dd28b6 |
45 | directory. |
46 | |
47 | If your local network does not allow you to use port 9418, then you can |
572f57ba |
48 | fetch a copy of the repository over HTTP (this is slower): |
d7dd28b6 |
49 | |
3b8a5fb0 |
50 | git clone http://perl5.git.perl.org/perl.git perl-http |
d7dd28b6 |
51 | |
f755e97d |
52 | This clones the repository and makes a local copy in the F<perl-http> |
d7dd28b6 |
53 | directory. |
54 | |
55 | =head2 WRITE ACCESS TO THE REPOSITORY |
56 | |
6acba58e |
57 | If you are a committer, then you can fetch a copy of the repository |
58 | that you can push back on with: |
d7dd28b6 |
59 | |
3b8a5fb0 |
60 | git clone ssh://perl5.git.perl.org/gitroot/perl.git perl-ssh |
d7dd28b6 |
61 | |
8f718e95 |
62 | This clones the repository and makes a local copy in the F<perl-ssh> |
d7dd28b6 |
63 | directory. |
64 | |
c26da522 |
65 | If you cloned using the git protocol, which is faster than ssh, then |
66 | you will need to modify your config in order to enable pushing. Edit |
67 | F<.git/config> where you will see something like: |
1a0f15d5 |
68 | |
69 | [remote "origin"] |
70 | url = git://perl5.git.perl.org/perl.git |
71 | |
72 | change that to something like this: |
73 | |
74 | [remote "origin"] |
75 | url = ssh://perl5.git.perl.org/gitroot/perl.git |
76 | |
dc3c3040 |
77 | NOTE: there are symlinks set up so that the /gitroot is optional and |
78 | since SSH is the default protocol you can actually shorten the "url" to |
79 | C<perl5.git.perl.org:/perl.git>. |
d7dd28b6 |
80 | |
184487f0 |
81 | You can also set up your user name and e-mail address. For example |
82 | |
83 | % git config user.name "Leon Brocard" |
84 | % git config user.email acme@astray.com |
85 | |
6acba58e |
86 | It is also possible to keep C<origin> as a git remote, and add a new |
87 | remote for ssh access: |
f6c12373 |
88 | |
dc3c3040 |
89 | % git remote add camel perl5.git.perl.org:/perl.git |
f6c12373 |
90 | |
6acba58e |
91 | This allows you to update your local repository by pulling from |
f755e97d |
92 | C<origin>, which is faster and doesn't require you to authenticate, and |
6acba58e |
93 | to push your changes back with the C<camel> remote: |
f6c12373 |
94 | |
95 | % git fetch camel |
96 | % git push camel |
97 | |
6acba58e |
98 | The C<fetch> command just updates the C<camel> refs, as the objects |
99 | themselves should have been fetched when pulling from C<origin>. |
f6c12373 |
100 | |
b47aa495 |
101 | The committers have access to 2 servers that serve perl5.git.perl.org. One is |
102 | camel.booking.com, which is the 'master' repository. The perl5.git.perl.org IP |
103 | address also lives on this machine. The second one is dromedary.booking.com, |
104 | which can be used for general testing and development. Dromedary syncs the git |
105 | tree from camel every few minutes, you should not push there. Both machines |
106 | also have a full CPAN mirror. To share files with the general public, dromedary |
107 | serves your ~/public_html/ as http://users.perl5.git.perl.org/~yourlogin/ |
108 | |
d7dd28b6 |
109 | =head1 OVERVIEW OF THE REPOSITORY |
110 | |
6acba58e |
111 | Once you have changed into the repository directory, you can inspect |
112 | it. |
d7dd28b6 |
113 | |
39219fd3 |
114 | After a clone the repository will contain a single local branch, which |
50eca761 |
115 | will be the current branch as well, as indicated by the asterisk. |
39219fd3 |
116 | |
117 | % git branch |
118 | * blead |
119 | |
f755e97d |
120 | Using the -a switch to C<branch> will also show the remote tracking |
6acba58e |
121 | branches in the repository: |
39219fd3 |
122 | |
d9847473 |
123 | % git branch -a |
09081495 |
124 | * blead |
d7dd28b6 |
125 | origin/HEAD |
126 | origin/blead |
127 | ... |
128 | |
6acba58e |
129 | The branches that begin with "origin" correspond to the "git remote" |
130 | that you cloned from (which is named "origin"). Each branch on the |
131 | remote will be exactly tracked by theses branches. You should NEVER do |
132 | work on these remote tracking branches. You only ever do work in a |
133 | local branch. Local branches can be configured to automerge (on pull) |
134 | from a designated remote tracking branch. This is the case with the |
135 | default branch C<blead> which will be configured to merge from the |
136 | remote tracking branch C<origin/blead>. |
39219fd3 |
137 | |
d7dd28b6 |
138 | You can see recent commits: |
139 | |
c2cf2042 |
140 | % git log |
d7dd28b6 |
141 | |
6acba58e |
142 | And pull new changes from the repository, and update your local |
143 | repository (must be clean first) |
d7dd28b6 |
144 | |
145 | % git pull |
09081495 |
146 | |
6acba58e |
147 | Assuming we are on the branch C<blead> immediately after a pull, this |
148 | command would be more or less equivalent to: |
39219fd3 |
149 | |
150 | % git fetch |
151 | % git merge origin/blead |
152 | |
6acba58e |
153 | In fact if you want to update your local repository without touching |
154 | your working directory you do: |
39219fd3 |
155 | |
156 | % git fetch |
157 | |
6acba58e |
158 | And if you want to update your remote-tracking branches for all defined |
159 | remotes simultaneously you can do |
39219fd3 |
160 | |
161 | % git remote update |
162 | |
6acba58e |
163 | Neither of these last two commands will update your working directory, |
164 | however both will update the remote-tracking branches in your |
165 | repository. |
39219fd3 |
166 | |
09081495 |
167 | To switch to another branch: |
168 | |
169 | % git checkout origin/maint-5.8-dor |
170 | |
6051489b |
171 | To make a local branch of a remote branch: |
172 | |
173 | % git checkout -b maint-5.10 origin/maint-5.10 |
174 | |
09081495 |
175 | To switch back to blead: |
176 | |
177 | % git checkout blead |
c2cf2042 |
178 | |
39219fd3 |
179 | =head2 FINDING OUT YOUR STATUS |
180 | |
181 | The most common git command you will use will probably be |
182 | |
183 | % git status |
184 | |
6acba58e |
185 | This command will produce as output a description of the current state |
186 | of the repository, including modified files and unignored untracked |
187 | files, and in addition it will show things like what files have been |
188 | staged for the next commit, and usually some useful information about |
189 | how to change things. For instance the following: |
39219fd3 |
190 | |
191 | $ git status |
192 | # On branch blead |
193 | # Your branch is ahead of 'origin/blead' by 1 commit. |
194 | # |
195 | # Changes to be committed: |
196 | # (use "git reset HEAD <file>..." to unstage) |
197 | # |
198 | # modified: pod/perlrepository.pod |
199 | # |
200 | # Changed but not updated: |
201 | # (use "git add <file>..." to update what will be committed) |
202 | # |
203 | # modified: pod/perlrepository.pod |
204 | # |
205 | # Untracked files: |
206 | # (use "git add <file>..." to include in what will be committed) |
207 | # |
208 | # deliberate.untracked |
209 | |
6acba58e |
210 | This shows that there were changes to this document staged for commit, |
211 | and that there were further changes in the working directory not yet |
212 | staged. It also shows that there was an untracked file in the working |
213 | directory, and as you can see shows how to change all of this. It also |
0549aefb |
214 | shows that there is one commit on the working branch C<blead> which has |
215 | not been pushed to the C<origin> remote yet. B<NOTE>: that this output |
216 | is also what you see as a template if you do not provide a message to |
217 | C<git commit>. |
7f6effc7 |
218 | |
219 | Assuming we commit all the mentioned changes above: |
220 | |
221 | % git commit -a -m'explain git status and stuff about remotes' |
222 | Created commit daf8e63: explain git status and stuff about remotes |
223 | 1 files changed, 83 insertions(+), 3 deletions(-) |
224 | |
225 | We can re-run git status and see something like this: |
226 | |
227 | % git status |
228 | # On branch blead |
229 | # Your branch is ahead of 'origin/blead' by 2 commits. |
230 | # |
231 | # Untracked files: |
232 | # (use "git add <file>..." to include in what will be committed) |
233 | # |
234 | # deliberate.untracked |
235 | nothing added to commit but untracked files present (use "git add" to track) |
236 | |
39219fd3 |
237 | |
6acba58e |
238 | When in doubt, before you do anything else, check your status and read |
239 | it carefully, many questions are answered directly by the git status |
240 | output. |
39219fd3 |
241 | |
c2cf2042 |
242 | =head1 SUBMITTING A PATCH |
243 | |
244 | If you have a patch in mind for Perl, you should first get a copy of |
245 | the repository: |
246 | |
247 | % git clone git://perl5.git.perl.org/perl.git perl-git |
248 | |
249 | Then change into the directory: |
250 | |
251 | % cd perl-git |
252 | |
6acba58e |
253 | Alternatively, if you already have a Perl repository, you should ensure |
254 | that you're on the I<blead> branch, and your repository is up to date: |
12322d22 |
255 | |
256 | % git checkout blead |
257 | % git pull |
258 | |
0549aefb |
259 | (It's preferable to patch against the latest blead version, since |
260 | patches are usually integrated from blead to the maintenance branches. |
261 | This does not apply, obviously, in the rare case where your patch is |
262 | specific to a maintaince release.) |
a44f43ac |
263 | |
6acba58e |
264 | Now that we have everything up to date, we need to create a temporary |
265 | new branch for these changes and switch into it: |
b1fccde5 |
266 | |
a9b05323 |
267 | % git checkout -b orange |
23f8d33e |
268 | |
a9b05323 |
269 | which is the short form of |
270 | |
b1fccde5 |
271 | % git branch orange |
272 | % git checkout orange |
273 | |
c2cf2042 |
274 | Then make your changes. For example, if Leon Brocard changes his name |
275 | to Orange Brocard, we should change his name in the AUTHORS file: |
276 | |
277 | % perl -pi -e 's{Leon Brocard}{Orange Brocard}' AUTHORS |
278 | |
279 | You can see what files are changed: |
280 | |
281 | % git status |
f755e97d |
282 | # On branch orange |
c2cf2042 |
283 | # Changes to be committed: |
284 | # (use "git reset HEAD <file>..." to unstage) |
285 | # |
286 | # modified: AUTHORS |
287 | # |
288 | |
c2cf2042 |
289 | And you can see the changes: |
290 | |
291 | % git diff |
292 | diff --git a/AUTHORS b/AUTHORS |
293 | index 293dd70..722c93e 100644 |
294 | --- a/AUTHORS |
295 | +++ b/AUTHORS |
7df2e4bc |
296 | @@ -541,7 +541,7 @@ Lars Hecking <lhecking@nmrc.ucc.ie> |
c2cf2042 |
297 | Laszlo Molnar <laszlo.molnar@eth.ericsson.se> |
298 | Leif Huhn <leif@hale.dkstat.com> |
299 | Len Johnson <lenjay@ibm.net> |
300 | -Leon Brocard <acme@astray.com> |
301 | +Orange Brocard <acme@astray.com> |
302 | Les Peters <lpeters@aol.net> |
303 | Lesley Binks <lesley.binks@gmail.com> |
304 | Lincoln D. Stein <lstein@cshl.org> |
305 | |
306 | Now commit your change locally: |
307 | |
dc3c3040 |
308 | % git commit -a -m 'Rename Leon Brocard to Orange Brocard' |
c2cf2042 |
309 | Created commit 6196c1d: Rename Leon Brocard to Orange Brocard |
310 | 1 files changed, 1 insertions(+), 1 deletions(-) |
311 | |
dc3c3040 |
312 | You can examine your last commit with: |
313 | |
314 | % git show HEAD |
315 | |
316 | and if you are not happy with either the description or the patch |
c26da522 |
317 | itself you can fix it up by editing the files once more and then issue: |
dc3c3040 |
318 | |
319 | % git commit -a --amend |
320 | |
c2cf2042 |
321 | Now you should create a patch file for all your local changes: |
322 | |
2af192ee |
323 | % git format-patch origin |
c2cf2042 |
324 | 0001-Rename-Leon-Brocard-to-Orange-Brocard.patch |
325 | |
326 | You should now send an email to perl5-porters@perl.org with a |
dc3c3040 |
327 | description of your changes, and include this patch file as an |
c2cf2042 |
328 | attachment. |
329 | |
b1fccde5 |
330 | If you want to delete your temporary branch, you may do so with: |
331 | |
332 | % git checkout blead |
333 | % git branch -d orange |
334 | error: The branch 'orange' is not an ancestor of your current HEAD. |
335 | If you are sure you want to delete it, run 'git branch -D orange'. |
336 | % git branch -D orange |
337 | Deleted branch orange. |
7df2e4bc |
338 | |
a44f43ac |
339 | =head2 A note on derived files |
340 | |
341 | Be aware that many files in the distribution are derivative--avoid |
0549aefb |
342 | patching them, because git won't see the changes to them, and the build |
343 | process will overwrite them. Patch the originals instead. Most |
344 | utilities (like perldoc) are in this category, i.e. patch |
345 | utils/perldoc.PL rather than utils/perldoc. Similarly, don't create |
346 | patches for files under $src_root/ext from their copies found in |
347 | $install_root/lib. If you are unsure about the proper location of a |
348 | file that may have gotten copied while building the source |
349 | distribution, consult the C<MANIFEST>. |
a44f43ac |
350 | |
351 | =head2 A note on binary files |
352 | |
0549aefb |
353 | Since the patch(1) utility cannot deal with binary files, it's |
354 | important that you either avoid the use of binary files in your patch, |
355 | generate the files dynamically, or that you encode any binary files |
356 | using the F<uupacktool.pl> utility. |
a44f43ac |
357 | |
358 | Assuming you needed to include a gzip-encoded file for a module's test |
359 | suite, you might do this as follows using the F<uupacktool.pl> utility: |
360 | |
361 | $ perl uupacktool.pl -v -p -D lib/Some/Module/t/src/t.gz |
362 | Writing lib/Some/Module/t/src/t.gz into lib/Some/Module/t/src/t.gz.packed |
363 | |
364 | This will replace the C<t.gz> file with an encoded counterpart. During |
0549aefb |
365 | C<make test>, before any tests are run, perl's Makefile will restore |
366 | all the C<.packed> files mentioned in the MANIFEST to their original |
367 | name. This means that the test suite does not need to be aware of this |
368 | packing scheme and will not need to be altered. |
a44f43ac |
369 | |
370 | =head2 Getting your patch accepted |
371 | |
0549aefb |
372 | The first thing you should include with your patch is a description of |
373 | the problem that the patch corrects. If it is a code patch (rather |
374 | than a documentation patch) you should also include a small test case |
375 | that illustrates the bug (a patch to an existing test file is |
376 | preferred). |
a44f43ac |
377 | |
378 | If you are submitting a code patch there are several other things that |
379 | you need to do. |
380 | |
381 | =over 4 |
382 | |
383 | =item Comments, Comments, Comments |
384 | |
0549aefb |
385 | Be sure to adequately comment your code. While commenting every line |
386 | is unnecessary, anything that takes advantage of side effects of |
a44f43ac |
387 | operators, that creates changes that will be felt outside of the |
0549aefb |
388 | function being patched, or that others may find confusing should be |
389 | documented. If you are going to err, it is better to err on the side |
390 | of adding too many comments than too few. |
a44f43ac |
391 | |
392 | =item Style |
393 | |
0549aefb |
394 | In general, please follow the particular style of the code you are |
395 | patching. |
a44f43ac |
396 | |
0549aefb |
397 | In particular, follow these general guidelines for patching Perl |
398 | sources: |
a44f43ac |
399 | |
400 | 8-wide tabs (no exceptions!) |
401 | 4-wide indents for code, 2-wide indents for nested CPP #defines |
402 | try hard not to exceed 79-columns |
403 | ANSI C prototypes |
404 | uncuddled elses and "K&R" style for indenting control constructs |
405 | no C++ style (//) comments |
406 | mark places that need to be revisited with XXX (and revisit often!) |
407 | opening brace lines up with "if" when conditional spans multiple |
408 | lines; should be at end-of-line otherwise |
409 | in function definitions, name starts in column 0 (return value is on |
410 | previous line) |
411 | single space after keywords that are followed by parens, no space |
412 | between function name and following paren |
413 | avoid assignments in conditionals, but if they're unavoidable, use |
414 | extra paren, e.g. "if (a && (b = c)) ..." |
415 | "return foo;" rather than "return(foo);" |
416 | "if (!foo) ..." rather than "if (foo == FALSE) ..." etc. |
417 | |
418 | =item Testsuite |
419 | |
0549aefb |
420 | When submitting a patch you should make every effort to also include an |
421 | addition to perl's regression tests to properly exercise your patch. |
422 | Your testsuite additions should generally follow these guidelines |
423 | (courtesy of Gurusamy Sarathy <gsar@activestate.com>): |
a44f43ac |
424 | |
425 | Know what you're testing. Read the docs, and the source. |
426 | Tend to fail, not succeed. |
427 | Interpret results strictly. |
428 | Use unrelated features (this will flush out bizarre interactions). |
429 | Use non-standard idioms (otherwise you are not testing TIMTOWTDI). |
430 | Avoid using hardcoded test numbers whenever possible (the |
431 | EXPECTED/GOT found in t/op/tie.t is much more maintainable, |
432 | and gives better failure reports). |
433 | Give meaningful error messages when a test fails. |
434 | Avoid using qx// and system() unless you are testing for them. If you |
435 | do use them, make sure that you cover _all_ perl platforms. |
436 | Unlink any temporary files you create. |
437 | Promote unforeseen warnings to errors with $SIG{__WARN__}. |
438 | Be sure to use the libraries and modules shipped with the version |
439 | being tested, not those that were already installed. |
440 | Add comments to the code explaining what you are testing for. |
441 | Make updating the '1..42' string unnecessary. Or make sure that |
442 | you update it. |
443 | Test _all_ behaviors of a given operator, library, or function: |
444 | - All optional arguments |
445 | - Return values in various contexts (boolean, scalar, list, lvalue) |
446 | - Use both global and lexical variables |
447 | - Don't forget the exceptional, pathological cases. |
448 | |
449 | =back |
450 | |
7df2e4bc |
451 | =head1 ACCEPTING A PATCH |
452 | |
453 | If you have received a patch file generated using the above section, |
454 | you should try out the patch. |
455 | |
456 | First we need to create a temporary new branch for these changes and |
457 | switch into it: |
458 | |
a9b05323 |
459 | % git checkout -b experimental |
7df2e4bc |
460 | |
6acba58e |
461 | Patches that were formatted by C<git format-patch> are applied with |
462 | C<git am>: |
7df2e4bc |
463 | |
2af192ee |
464 | % git am 0001-Rename-Leon-Brocard-to-Orange-Brocard.patch |
7df2e4bc |
465 | Applying Rename Leon Brocard to Orange Brocard |
466 | |
6acba58e |
467 | If just a raw diff is provided, it is also possible use this two-step |
468 | process: |
09645c26 |
469 | |
470 | % git apply bugfix.diff |
dc3c3040 |
471 | % git commit -a -m "Some fixing" --author="That Guy <that.guy@internets.com>" |
09645c26 |
472 | |
7df2e4bc |
473 | Now we can inspect the change: |
474 | |
dc3c3040 |
475 | % git show HEAD |
7df2e4bc |
476 | commit b1b3dab48344cff6de4087efca3dbd63548ab5e2 |
477 | Author: Leon Brocard <acme@astray.com> |
478 | Date: Fri Dec 19 17:02:59 2008 +0000 |
479 | |
480 | Rename Leon Brocard to Orange Brocard |
7df2e4bc |
481 | |
7df2e4bc |
482 | diff --git a/AUTHORS b/AUTHORS |
483 | index 293dd70..722c93e 100644 |
484 | --- a/AUTHORS |
485 | +++ b/AUTHORS |
486 | @@ -541,7 +541,7 @@ Lars Hecking <lhecking@nmrc.ucc.ie> |
487 | Laszlo Molnar <laszlo.molnar@eth.ericsson.se> |
488 | Leif Huhn <leif@hale.dkstat.com> |
489 | Len Johnson <lenjay@ibm.net> |
490 | -Leon Brocard <acme@astray.com> |
491 | +Orange Brocard <acme@astray.com> |
492 | Les Peters <lpeters@aol.net> |
493 | Lesley Binks <lesley.binks@gmail.com> |
494 | Lincoln D. Stein <lstein@cshl.org> |
495 | |
496 | If you are a committer to Perl and you think the patch is good, you can |
75fb7651 |
497 | then merge it into blead then push it out to the main repository: |
7df2e4bc |
498 | |
499 | % git checkout blead |
d9847473 |
500 | % git merge experimental |
75fb7651 |
501 | % git push |
7df2e4bc |
502 | |
503 | If you want to delete your temporary branch, you may do so with: |
504 | |
505 | % git checkout blead |
506 | % git branch -d experimental |
507 | error: The branch 'experimental' is not an ancestor of your current HEAD. |
508 | If you are sure you want to delete it, run 'git branch -D experimental'. |
509 | % git branch -D experimental |
510 | Deleted branch experimental. |
b0d36535 |
511 | |
512 | =head1 CLEANING A WORKING DIRECTORY |
513 | |
6acba58e |
514 | The command C<git clean> can with varying arguments be used as a |
dc3c3040 |
515 | replacement for C<make clean>. |
b0d36535 |
516 | |
517 | To reset your working directory to a pristine condition you can do: |
518 | |
519 | git clean -dxf |
520 | |
521 | However, be aware this will delete ALL untracked content. You can use |
522 | |
523 | git clean -Xf |
524 | |
6acba58e |
525 | to remove all ignored untracked files, such as build and test |
526 | byproduct, but leave any manually created files alone. |
b0d36535 |
527 | |
0549aefb |
528 | If you only want to cancel some uncommitted edits, you can use C<git |
c26da522 |
529 | checkout> and give it a list of files to be reverted, or C<git checkout |
530 | -f> to revert them all. |
f755e97d |
531 | |
532 | If you want to cancel one or several commits, you can use C<git reset>. |
533 | |
d82a90c1 |
534 | =head1 BISECTING |
535 | |
6acba58e |
536 | C<git> provides a built-in way to determine, with a binary search in |
537 | the history, which commit should be blamed for introducing a given bug. |
d82a90c1 |
538 | |
6acba58e |
539 | Suppose that we have a script F<~/testcase.pl> that exits with C<0> |
540 | when some behaviour is correct, and with C<1> when it's faulty. We need |
541 | an helper script that automates building C<perl> and running the |
542 | testcase: |
d82a90c1 |
543 | |
544 | % cat ~/run |
545 | #!/bin/sh |
546 | git clean -dxf |
547 | # If you can use ccache, add -Dcc=ccache\ gcc -Dld=gcc to the Configure line |
c0d1ef72 |
548 | sh Configure -des -Dusedevel -Doptimize="-g" |
549 | test -f config.sh || exit 125 |
550 | # Correct makefile for newer GNU gcc |
551 | perl -ni -we 'print unless /<(?:built-in|command)/' makefile x2p/makefile |
552 | # if you just need miniperl, replace test_prep with miniperl |
553 | make -j4 test_prep |
554 | -x ./perl || exit 125 |
d82a90c1 |
555 | ./perl -Ilib ~/testcase.pl |
c0d1ef72 |
556 | ret=$? |
557 | git clean -dxf |
558 | exit $ret |
d82a90c1 |
559 | |
6acba58e |
560 | This script may return C<125> to indicate that the corresponding commit |
561 | should be skipped. Otherwise, it returns the status of |
562 | F<~/testcase.pl>. |
d82a90c1 |
563 | |
564 | We first enter in bisect mode with: |
565 | |
566 | % git bisect start |
567 | |
6acba58e |
568 | For example, if the bug is present on C<HEAD> but wasn't in 5.10.0, |
569 | C<git> will learn about this when you enter: |
d82a90c1 |
570 | |
571 | % git bisect bad |
572 | % git bisect good perl-5.10.0 |
573 | Bisecting: 853 revisions left to test after this |
574 | |
6acba58e |
575 | This results in checking out the median commit between C<HEAD> and |
576 | C<perl-5.10.0>. We can then run the bisecting process with: |
d82a90c1 |
577 | |
578 | % git bisect run ~/run |
579 | |
580 | When the first bad commit is isolated, C<git bisect> will tell you so: |
581 | |
582 | ca4cfd28534303b82a216cfe83a1c80cbc3b9dc5 is first bad commit |
583 | commit ca4cfd28534303b82a216cfe83a1c80cbc3b9dc5 |
584 | Author: Dave Mitchell <davem@fdisolutions.com> |
585 | Date: Sat Feb 9 14:56:23 2008 +0000 |
586 | |
9469eb4a |
587 | [perl #49472] Attributes + Unknown Error |
d82a90c1 |
588 | ... |
589 | |
590 | bisect run success |
591 | |
6acba58e |
592 | You can peek into the bisecting process with C<git bisect log> and |
593 | C<git bisect visualize>. C<git bisect reset> will get you out of bisect |
594 | mode. |
d82a90c1 |
595 | |
6acba58e |
596 | Please note that the first C<good> state must be an ancestor of the |
597 | first C<bad> state. If you want to search for the commit that I<solved> |
598 | some bug, you have to negate your test case (i.e. exit with C<1> if OK |
599 | and C<0> if not) and still mark the lower bound as C<good> and the |
600 | upper as C<bad>. The "first bad commit" has then to be understood as |
601 | the "first commit where the bug is solved". |
d82a90c1 |
602 | |
6acba58e |
603 | C<git help bisect> has much more information on how you can tweak your |
604 | binary searches. |
9d68b7ed |
605 | |
03050721 |
606 | =head1 SUBMITTING A PATCH VIA GITHUB |
607 | |
608 | GitHub is a website that makes it easy to fork and publish projects |
609 | with Git. First you should set up a GitHub account and log in. |
610 | |
611 | Perl's git repository is mirrored on GitHub at this page: |
612 | |
613 | http://github.com/github/perl/tree/blead |
614 | |
615 | Visit the page and click the "fork" button. This clones the Perl git |
616 | repository for you and provides you with "Your Clone URL" from which |
617 | you should clone: |
618 | |
619 | % git clone git@github.com:USERNAME/perl.git perl-github |
620 | |
621 | We shall make the same patch as above, creating a new branch: |
622 | |
623 | % cd perl-github |
624 | % git remote add upstream git://github.com/github/perl.git |
625 | % git pull upstream blead |
626 | % git checkout -b orange |
627 | % perl -pi -e 's{Leon Brocard}{Orange Brocard}' AUTHORS |
dc3c3040 |
628 | % git commit -a -m 'Rename Leon Brocard to Orange Brocard' |
03050721 |
629 | % git push origin orange |
630 | |
631 | The orange branch has been pushed to GitHub, so you should now send an |
632 | email to perl5-porters@perl.org with a description of your changes and |
633 | the following information: |
634 | |
635 | http://github.com/USERNAME/perl/tree/orange |
636 | git@github.com:USERNAME/perl.git branch orange |
637 | |
c26da522 |
638 | =head1 MERGING FROM A BRANCH VIA GITHUB |
639 | |
640 | If someone has provided a branch via GitHub and you are a committer, |
5c9c28c6 |
641 | you should use the following in your perl-ssh directory: |
c26da522 |
642 | |
643 | % git remote add dandv git://github.com/dandv/perl.git |
644 | % git fetch |
645 | |
646 | Now you can see the differences between the branch and blead: |
647 | |
648 | % git diff dandv/blead |
649 | |
650 | And you can see the commits: |
651 | |
652 | % git log dandv/blead |
653 | |
654 | If you approve of a specific commit, you can cherry pick it: |
655 | |
2bab0636 |
656 | % git cherry-pick 3adac458cb1c1d41af47fc66e67b49c8dec2323f |
657 | |
658 | Or you could just merge the whole branch if you like it all: |
659 | |
660 | % git merge dandv/blead |
c26da522 |
661 | |
662 | And then push back to the repository: |
663 | |
664 | % git push |
665 | |
9469eb4a |
666 | =head1 COMMITTING TO MAINTENANCE VERSIONS |
9d68b7ed |
667 | |
668 | To commit to a maintenance version of perl, you need to create a local |
669 | tracking branch: |
670 | |
671 | % git checkout --track -b maint-5.005 origin/maint-5.005 |
672 | |
0549aefb |
673 | This creates a local branch named C<maint-5.005>, which tracks the |
674 | remote branch C<origin/maint-5.005>. Then you can pull, commit, merge |
675 | and push as before. |
b0d36535 |
676 | |
f755e97d |
677 | You can also cherry-pick commits from blead and another branch, by |
0549aefb |
678 | using the C<git cherry-pick> command. It is recommended to use the |
679 | B<-x> option to C<git cherry-pick> in order to record the SHA1 of the |
680 | original commit in the new commit message. |
f755e97d |
681 | |
682 | =head1 SEE ALSO |
683 | |
684 | The git documentation, accessible via C<git help command>. |
0549aefb |
685 | |