{"thread":{"id":"15872","subject":"What's cooking in git/spearce.git (Oct 2008, #02; Sun, 12)","startedAt":"2008-10-12T21:25:43Z","lastAt":"2008-10-13T23:17:16Z","messageCount":6,"participants":["Shawn O. Pearce","Junio C Hamano","Stephen Haberman","Nanako Shiraishi"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"92876","messageId":"20081012212543.GG4856@spearce.org","threadId":"15872","inReplyTo":null,"subject":"What's cooking in git/spearce.git (Oct 2008, #02; Sun, 12)","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-10-12T21:25:43Z","receivedAt":"2008-10-12T21:25:43Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"What's cooking in git/spearce.git (Oct 2008, #02; Sun, 12)\n--------------------------------------------------\n\nHere are the topics that have been cooking. Commits prefixed\nwith '-' are only in 'pu' while commits prefixed with '+' are\nin 'next'.\n\nThe topics list the commits in reverse chronological order. The topics\nmeant to be merged to the maintenance series have \"maint-\" in their names.\n\ngitster's back and I'm expecting he will take over from here.\n\n----------------------------------------------------------------\n[New Topics]\n\n* dp/checkattr (Tue Oct 7 04:16:52 2008 +0400) 2 commits\n + check-attr: Add --stdin option\n + check-attr: add an internal check_attr() function\n\nBatch attr lookup via --stdin, for gitk and git-gui.\n\n* mv/clonev (Thu Oct 9 01:40:32 2008 +0200) 1 commit\n + Implement git clone -v\n\nDoes what it says it does. This may be ready for master soon,\nits a pretty trivial change.\n\n* gb/refactor-pathinfo (Fri Oct 10 20:42:26 2008 +0200) 1 commit\n + gitweb: refactor input parameters parse/validation\n\nA major cleanup on the way gitweb parses its input arguments.\nFuture gitweb patches to add more arguments into the PATH_INFO\ndepend upon this initial cleanup work.\n\n* ml/cygwin-filemode (Sun Oct 12 14:44:46 2008 -0400) 1 commit\n - compat/cygwin.c - Use cygwin's stat if core.filemode == true\n\nI think another version may be coming to reuse the core.filemode\nparsing so this patch isn't in next yet.\n\n* sh/rebase-i-p (Wed Oct 8 01:41:57 2008 -0500) 7 commits\n - rebase-i-p: if todo was reordered use HEAD as the rewritten parent\n - rebase-i-p: do not include non-first-parent commits touching\n UPSTREAM\n - rebase-i-p: only list commits that require rewriting in todo\n - rebase-i-p: fix 'no squashing merges' tripping up non-merges\n - rebase-i-p: delay saving current-commit to REWRITTEN if squashing\n - rebase-i-p: use HEAD for updating the ref instead of mapping\n OLDHEAD\n - rebase-i-p: test to exclude commits from todo based on its parents\n\nChanges the `rebase -i -p` behavior to behave like git sequencer's\nrewrite of `rebase -i` would behave. Its parked in pu because I\nhave not had the time to review the series in detail. First glance\nlooked OK to me.\n\n* js/keephardlinks (Sat Oct 11 13:45:13 2008 +0200) 1 commit\n - Introduce core.keepHardLinks\n\nThe value of this change is currently in question, and the commit\nmessage doesn't justify it very well.\n\n* jn/gitweb-customlinks (Sun Oct 12 00:02:32 2008 +0200) 1 commit\n - gitweb: Better processing format string in custom links in navbar\n\nWaiting for some sort of response from Pasky.\n\n----------------------------------------------------------------\n[Graduated to \"master\"]\n\n* mw/sendemail (Sun Sep 28 07:51:21 2008 +0300) 10 commits\n + bash completion: Add --[no-]validate to \"git send-email\"\n + send-email: signedoffcc -> signedoffbycc, but handle both\n + Docs: send-email: Create logical groupings for man text\n + Docs: send-email: Create logical groupings for --help text\n + Docs: send-email: Remove unnecessary config variable description\n + Docs: send-email: --chain_reply_to -> --[no-]chain-reply-to\n + send-email: change --no-validate to boolean --[no-]validate\n + Docs: send-email: Man page option ordering\n + Docs: send-email usage text much sexier\n + Docs: send-email's usage text and man page mention same options\n\n* jc/add-ita (Thu Aug 21 01:44:53 2008 -0700) 1 commit\n + git-add --intent-to-add (-N)\n\n* mg/verboseprune (Mon Sep 29 18:49:52 2008 +0200) 1 commit\n + make prune report removed objects on -v\n\n* lt/time-reject-fractional-seconds (Sat Aug 16 21:25:40 2008 -0700) 1 commit\n + date/time: do not get confused by fractional seconds\n\n* dp/cywginstat (Tue Sep 30 17:53:47 2008 +0400) 3 commits\n + cygwin: Use native Win32 API for stat\n + mingw: move common functionality to win32.h\n + add have_git_dir() function\n\nPerformance improvement for Cygwin, bypassing the Cygwin stat\nfunction and using one more like MinGW uses. Probably ready for\nmaster on the next round. Several Cygwin users have given praise\nto the series.\n\n* js/objc-funchdr (Wed Oct 1 00:46:34 2008 +0100) 1 commit\n + Teach git diff about Objective-C syntax\n\nAdds support for Objective-C function headers.\n\n* dm/svn-branch (Sat Oct 4 19:35:17 2008 -0700) 1 commit\n + Add git-svn branch to allow branch creation in SVN repositories\n\nAdds \"git svn branch\" to build branches remotely in SVN.\n\n* pb/gitweb (Fri Oct 3 07:41:25 2008 -0700) 7 commits\n + Merge branch 'pb/gitweb-tagcloud' into pb/gitweb\n + gitweb: Support for simple project search form\n + gitweb: Make the by_tag filter delve in forks as well\n + gitweb: Support for tag clouds\n + gitweb: Add support for extending the action bar with custom links\n + gitweb: Sort the list of forks on the summary page by age\n + gitweb: Clean-up sorting of project list\n\n* ph/parseopt (Thu Oct 2 14:59:20 2008 +0200) 3 commits\n + parse-opt: migrate builtin-merge-file.\n + parse-opt: migrate git-merge-base.\n + parse-opt: migrate fmt-merge-msg.\n\n* rz/grepz (Wed Oct 1 18:11:15 2008 +0200) 1 commit\n + git grep: Add \"-z/--null\" option as in GNU's grep.\n\n* mv/merge-refresh (Fri Oct 3 15:02:31 2008 +0200) 1 commit\n + builtin-merge: refresh the index before calling a strategy\n\n* bc/xdiffnl (Wed Oct 1 14:28:26 2008 -0500) 1 commit\n + xdiff-interface.c: strip newline (and cr) from line before pattern\n matching\n\n* jk/maint-soliconv (Fri Oct 3 02:39:36 2008 -0400) 1 commit\n + Makefile: do not set NEEDS_LIBICONV for Solaris 8\n\n* sg/maint-intrebase-msghook (Fri Oct 3 11:33:20 2008 +0200) 2 commits\n + rebase -i: remove leftover debugging\n + rebase -i: proper prepare-commit-msg hook argument when squashing\n\n* bc/maint-stashref (Thu Oct 2 18:52:11 2008 -0500) 1 commit\n + git-stash.sh: fix flawed fix of invalid ref handling (commit\n da65e7c1)\n\nThe latter three were merged to 'maint' first.\n\n----------------------------------------------------------------\n[Old New Topics]\n\n* ns/rebase-noverify (Mon Oct 6 14:14:29 2008 +0900) 1 commit\n + rebase --no-verify\n\nThis adds --no-verify to git rebase, to avoid the pre-rebase hook.\nLacks documentation but otherwise looks sound.\n\n* mv/merge-noff (Fri Oct 3 14:04:47 2008 +0200) 1 commit\n + builtin-commit: use reduce_heads() only when appropriate\n\nFixes \"git merge --no-ff --no-commit\".\n\n* ae/preservemerge (Mon Sep 29 22:28:57 2008 +0200) 1 commit\n + rebase: Support preserving merges in non-interactive mode\n\n* sh/maint-rebase3 (Sun Oct 5 23:26:52 2008 -0500) 1 commit\n - rebase--interactive: fix parent rewriting for dropped commits\n\nA prior version of sh/rebase-i-p. This should be dropped.\n\n* pb/rename-rowin32 (Fri Oct 3 12:20:43 2008 +0200) 1 commit\n - Do not rename read-only files during a push\n\nSupposedly fixes pack file renames on Windows, but it makes the\ntest suite fail on Linux. I haven't debugged why yet. Its very\nlikely we need a replacement patch before this can move forward.\n\n* sp/describe-lwtag (Tue Sep 30 12:03:41 2008 -0700) 1 commit\n - describe: Make --tags and --all match lightweight tags more often\n\nBased on feedback from the list this needs another spin. I will\npost a replacement patch soon.\n\n* gb/formatpatch-autonbr (Thu Oct 2 16:55:39 2008 -0400) 1 commit\n - format-patch: autonumber by default\n\nFails the test suite; some of the test vectors need to be updated\nto account for the new default. Someone who cares about this\nchange should follow through on the test suite update, or this may\nget dropped.\n\n* jc/merge-whitespace (Sun Feb 24 23:29:36 2008 -0800) 1 commit\n . WIP: start teaching the --whitespace=fix to merge machinery\n\nThis has a merge conflict with `next` and isn't even in pu right now.\n\n* jk/diff-convfilter (Sun Oct 5 17:43:45 2008 -0400) 4 commits\n - diff: add filter for converting binary to text\n - diff: introduce diff..binary\n - diff: unify external diff and funcname parsing code\n - t4012: use test_cmp instead of cmp\n\nA general cleanup on how diff drivers are implemented. Its still\nmissing documentation updates and tests but doesn't break anything\ncurrent as far as I can tell. It needs more review before it can\nbe slated for 'next'.\n\n----------------------------------------------------------------\n[Stuck Topics]\n\n* nd/narrow (Wed Oct 1 11:04:09 2008 +0700) 9 commits\n - grep: skip files outside sparse checkout area\n - checkout_entry(): CE_NO_CHECKOUT on checked out entries.\n - Prevent diff machinery from examining worktree outside sparse\n checkout\n - ls-files: Add tests for --sparse and friends\n - update-index: add --checkout/--no-checkout to update\n CE_NO_CHECKOUT bit\n - update-index: refactor mark_valid() in preparation for new options\n - ls-files: add options to support sparse checkout\n - Introduce CE_NO_CHECKOUT bit\n - Extend index to save more flags\n\nRecently updated with a repost. I've been too swamped at day-job\nto actively review the series. There has been some discussion on\nlist about it so its not stalled, but it needs more eyeballs.\n\n* gb/gitweb-pathinfo (Thu Oct 2 02:10:34 2008 +0200) 6 commits\n . gitweb: generate parent..current URLs\n . gitweb: parse parent..current syntax from pathinfo\n . gitweb: use_pathinfo filenames start with /\n . gitweb: generate project/action/hash URLs\n . gitweb: refactor input parameters parse/validation\n . gitweb: parse project/action/hash_base:filename PATH_INFO\n\nStill going through revisions on the git ML. Its great work and\nis heading in the right direction. But the discussion and patch\ngeneration rate is too high to merge the topic into next just yet.\n\nSo its waiting for a re-roll of the series once discussion settles\ndown and there is a final patch series available.\n\n----------------------------------------------------------------\n[Stalled -- Needs Action to Proceed (or to be dropped)]\n\n* pb/submodule (Fri Sep 12 23:09:19 2008 +0200) 1 commit\n - t7400: Add short \"git submodule add\" testsuite\n\nStill waiting for a reroll. Should be dropped next week if we\ndon't get one during this coming week.\n\n* bd/blame (Thu Aug 21 18:22:01 2008 -0500) 5 commits\n - Use xdiff caching to improve git blame performance\n - Allow xdiff machinery to cache hash results for a file\n - Always initialize xpparam_t to 0\n - Bypass textual patch generation and parsing in git blame\n - Allow alternate \"low-level\" emit function from xdl_diff\n\n(jc: Réne had good comments on how the callback should be\n structured.)\n\n* kb/am-directory (Fri Aug 29 15:27:50 2008 -0700) 1 commit\n - git-am: Pass the --directory option through to git-apply\n\n(jc: I think this is still buggy and drops the option when am stops\n with conflicts.)\n\n----------------------------------------------------------------\n[Will be merged to 'master/maint' soon]\n\n* pb/commit-where (Fri Oct 3 22:13:49 2008 -0400) 4 commits\n + tutorial: update output of git commit\n + reformat informational commit message\n + git commit: Reformat output somewhat\n + builtin-commit.c: show on which branch a commit was added\n\nI think this topic is settled for now.\n\n----------------------------------------------------------------\n[Actively Cooking]\n\n* tr/workflow-doc (Sat Sep 13 18:11:01 2008 +0200) 2 commits\n + Documentation: Refer to git-rebase(1) to warn against rewriting\n + Documentation: new upstream rebase recovery section in git-rebase\n\n(jc: My impression from the last round of discusson on the third\n patch in this series (not queued here) was that as long as we\n do not present it as \"One True Workflow\", the description was\n a good starting point, possibly others to add other recommended\n flows later.)\n\nAn update came in recently, but I haven't applied it.\n\n----------------------------------------------------------------\n[On Hold]\n\n* jc/post-simplify (Fri Aug 15 01:34:51 2008 -0700) 2 commits\n - revision --simplify-merges: incremental simplification\n - revision --simplify-merges: prepare for incremental simplification\n\n(jc: I started making this incremental but the progress is not\n so great.)\n\n* jc/stripspace (Sun Mar 9 00:30:35 2008 -0800) 6 commits\n . git-am --forge: add Signed-off-by: line for the author\n . git-am: clean-up Signed-off-by: lines\n . stripspace: add --log-clean option to clean up signed-off-by:\n lines\n . stripspace: use parse_options()\n . Add \"git am -s\" test\n . git-am: refactor code to add signed-off-by line for the committer\n\n(jc: The one at second from the tip needs reworking.)\n\n* jc/send-pack-tell-me-more (Thu Mar 20 00:44:11 2008 -0700) 1 commit\n - \"git push\": tellme-more protocol extension\n\nThis is a great idea, but IIRC its implementation has a deadlock\nduring communication between the peers. Someone needs to pick up\nthis topic and resolve the deadlock before it can continue.\n\n* jc/blame (Wed Jun 4 22:58:40 2008 -0700) 2 commits\n - blame: show \"previous\" information in --porcelain/--incremental\n format\n - git-blame: refactor code to emit \"porcelain format\" output\n\n* jk/renamelimit (Sat May 3 13:58:42 2008 -0700) 1 commit\n - diff: enable \"too large a rename\" warning when -M/-C is explicitly\n asked for\n\n(jc: This would be the right thing to do for command line use,\n but gitk will be hit due to tcl/tk's limitation, so I am holding\n this back for now.)\n-- \nShawn.\n"},{"id":"92892","messageId":"7v3aj1fdw2.fsf@gitster.siamese.dyndns.org","threadId":"15872","inReplyTo":"20081012212543.GG4856@spearce.org","subject":"Re: What's cooking in git/spearce.git (Oct 2008, #02; Sun, 12)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-10-13T02:05:33Z","receivedAt":"2008-10-13T02:05:33Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Shawn O. Pearce\" writes:\n\n> * pb/rename-rowin32 (Fri Oct 3 12:20:43 2008 +0200) 1 commit\n> - Do not rename read-only files during a push\n>\n> Supposedly fixes pack file renames on Windows, but it makes the\n> test suite fail on Linux. I haven't debugged why yet.\n\nI am kind of surprised that it actually passes the test on Windows, which\nimplies that these cats shown in the patch to fix this breakage below do\nnot honor ro-ness of the file, which in turn makes me doubt if making the\nresulting packfiles read-only has any effect on that platform whatsoever..\n\n t/t5300-pack-object.sh | 2 ++\n 1 files changed, 2 insertions(+), 0 deletions(-)\n\ndiff --git i/t/t5300-pack-object.sh w/t/t5300-pack-object.sh\nindex b335c6b..544f59e 100755\n--- i/t/t5300-pack-object.sh\n+++ w/t/t5300-pack-object.sh\n@@ -248,6 +248,7 @@ test_expect_success \\\n git index-pack test-3.pack &&\n cmp test-3.idx test-1-${packname_1}.idx &&\n \n+ rm -f test-3.pack &&\n cat test-2-${packname_2}.pack >test-3.pack &&\n git index-pack -o tmp.idx test-2-${packname_2}.pack &&\n cmp tmp.idx test-2-${packname_2}.idx &&\n@@ -255,6 +256,7 @@ test_expect_success \\\n git index-pack test-3.pack &&\n cmp test-3.idx test-2-${packname_2}.idx &&\n \n+ rm -f test-3.pack &&\n cat test-3-${packname_3}.pack >test-3.pack &&\n git index-pack -o tmp.idx test-3-${packname_3}.pack &&\n cmp tmp.idx test-3-${packname_3}.idx &&\n"},{"id":"92895","messageId":"7vprm5duhq.fsf@gitster.siamese.dyndns.org","threadId":"15872","inReplyTo":"7v3aj1fdw2.fsf@gitster.siamese.dyndns.org","subject":"Re: What's cooking in git/spearce.git (Oct 2008, #02; Sun, 12)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-10-13T03:49:53Z","receivedAt":"2008-10-13T03:49:53Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Junio C Hamano writes:\n\n> \"Shawn O. Pearce\" writes:\n>\n>> * pb/rename-rowin32 (Fri Oct 3 12:20:43 2008 +0200) 1 commit\n>> - Do not rename read-only files during a push\n>>\n>> Supposedly fixes pack file renames on Windows, but it makes the\n>> test suite fail on Linux. I haven't debugged why yet.\n>\n> I am kind of surprised that it actually passes the test on Windows, which\n> implies that these cats shown in the patch to fix this breakage below do\n> not honor ro-ness of the file, which in turn makes me doubt if making the\n> resulting packfiles read-only has any effect on that platform whatsoever..\n\nActually, the patch I posted was wrong and shouldn't be applied, as the\noriginal breakage is a sign that the externally observable behaviour of\nthe command has changed, and the patch was just hiding it under the rug.\n\nThe thing is that 8c76006 (Do not rename read-only files during a push,\n2008-10-03) makes unnecessary chmod() when there is no rename is involved,\nnamely when it is used to index an existing packfile on the filesystem.\n\nI think the attached patch is a better fix, to be squashed in.\n\nNote: I now have the pumpkin, so you do not have to apply and push the\nresults out --- this is just me showing a proposed change as usual.\n\n index-pack.c | 3 ++-\n 1 files changed, 2 insertions(+), 1 deletions(-)\n\ndiff --git c/index-pack.c w/index-pack.c\nindex 2c69f08..aec11cb 100644\n--- c/index-pack.c\n+++ w/index-pack.c\n@@ -823,7 +823,8 @@ static void final(const char *final_pack_name, const char *curr_pack_name,\n \t\tif (move_temp_to_file(curr_pack_name, final_pack_name))\n \t\t\tdie(\"cannot store pack file\");\n \t}\n-\tchmod(final_pack_name, 0444);\n+\tif (from_stdin)\n+\t\tchmod(final_pack_name, 0444);\n \n \tif (final_index_name != curr_index_name) {\n \t\tif (!final_index_name) {\n"},{"id":"92906","messageId":"20081013013752.8fc16695.stephen@exigencecorp.com","threadId":"15872","inReplyTo":"20081012212543.GG4856@spearce.org","subject":"Re: What's cooking in git/spearce.git (Oct 2008, #02; Sun, 12)","fromName":"Stephen Haberman","fromEmail":"stephen@exigencecorp.com","sentAt":"2008-10-13T06:37:52Z","receivedAt":"2008-10-13T06:37:52Z","isPatch":false,"sender":{"key":"stephen@exigencecorp.com","avatar":"https://gravatar.com/avatar/23b93ad70a06ce53505f17ddba65176edbcfb6588e7a4c1a2dca04aaf0a6aff1?d=mp&s=160"},"body":"\n> * sh/maint-rebase3 (Sun Oct 5 23:26:52 2008 -0500) 1 commit\n> - rebase--interactive: fix parent rewriting for dropped commits\n> \n> A prior version of sh/rebase-i-p. This should be dropped.\n\nmaint-rebase3 is actually a separate issue than sh/rebase-i-p.\n\nmaint-rebase3 deals with commits dropped because they are recognized as\ncherry picks, while rebase-i-p deals with commits that can be ignored\nfrom the todo because their parents are not being changed.\n\nI'm surprised they both applied cleanly to pu--I was expecting a\nconflict, as I noted in one of my posts. I just fetched pu and they\nseem to have each broke the each other's tests as well.\n\nTo fix this, I have some local changes to pu that gets both tests\npassing again. Should I submit my integration changes as a diff on top\nof pu? Or should I try and integrate the two patches into one series?\n\nTechnically these two fixes are different things, and I assert you\ncould apply one or the other, but if you apply both, they require\nintegration, so I'm not sure what to do.\n\n(...nuts, t3404#22 is failing, so my maint3-rebase/rebase-i-p\nintegration patch is not quite ready yet.)\n\n(I also have a test comment typo and test_expect_failure change to make\nto rebase-i-p from Junio's feedback and would like to know the\npreferred way to submit those--e.g. a patch on top of your pu, a patch\non top of the existing series, or a new series all together. Given it\nis not next, I'm guessing a new series all together.)\n\nThanks,\nStephen\n"},{"id":"92934","messageId":"7vhc7gbmhe.fsf@gitster.siamese.dyndns.org","threadId":"15872","inReplyTo":"20081013013752.8fc16695.stephen@exigencecorp.com","subject":"Re: What's cooking in git/spearce.git (Oct 2008, #02; Sun, 12)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-10-13T14:25:49Z","receivedAt":"2008-10-13T14:25:49Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Stephen Haberman writes:\n\n> (I also have a test comment typo and test_expect_failure change to make\n> to rebase-i-p from Junio's feedback and would like to know the\n> preferred way to submit those--e.g. a patch on top of your pu, a patch\n> on top of the existing series, or a new series all together. Given it\n> is not next, I'm guessing a new series all together.)\n\nYou guessed it right.\n\nAs sh/maint-rebase3 is about a pure fix, while the other -i-p is a more\ninvolved enhancement, I am guessing Shawn decided not to queue the latter\nfor 1.6.0.X, and I agree with that. The final shape of the history should\nlook like:\n\n * maint will eventually get sh/maint-rebase3 to be in 1.6.0.X, which in\n turn will eventually be merged to master;\n\n * master will eventually get sh/rebase-i-p.\n\nWhen two series have dependencies like this, it is generally the easiest\nand cleanest to prepare them to match such a final shape of the history.\nHence, we would want two series built like this:\n\n * sh/maint-rebase3 applicable to the tip of 'maint' (this is already done;\n what is in sh/maint-rebase3 is exactly that);\n\n * apply the above locally to 'maint', merge the result locally to\n 'master', and prepare sh/rebase-i-p series applicable on top of that\n merge.\n\nThanks.\n"},{"id":"92981","messageId":"20081014081716.6117@nanako3.lavabit.com","threadId":"15872","inReplyTo":"20081012212543.GG4856@spearce.org","subject":"[PATCH] rebase: Document --no-verify option to bypass pre-rebase hook","fromName":"Nanako Shiraishi","fromEmail":"nanako3@lavabit.com","sentAt":"2008-10-13T23:17:16Z","receivedAt":"2008-10-13T23:17:16Z","isPatch":true,"sender":{"key":"nanako3@lavabit.com","avatar":"https://gravatar.com/avatar/3777b9e201c5883a62b1a6fdf7c53f2d712d1d80989146063ea861e33aad72a8?d=mp&s=160"},"body":"Signed-off-by: Nanako Shiraishi \n---\n\n\"Shawn O. Pearce\" writes:\n\n> * ns/rebase-noverify (Mon Oct 6 14:14:29 2008 +0900) 1 commit\n> + rebase --no-verify\n>\n> This adds --no-verify to git rebase, to avoid the pre-rebase hook.\n> Lacks documentation but otherwise looks sound.\n\nHere it is.\n\n Documentation/git-rebase.txt | 5 ++++-\n 1 files changed, 4 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt\nindex 32f0f12..4e84380 100644\n--- a/Documentation/git-rebase.txt\n+++ b/Documentation/git-rebase.txt\n@@ -9,7 +9,7 @@ SYNOPSIS\n --------\n [verse]\n 'git rebase' [-i | --interactive] [-v | --verbose] [-m | --merge]\n-\t[-s | --strategy=]\n+\t[-s | --strategy=] [--no-verify]\n \t[-C] [ --whitespace=