{"thread":{"id":"21877","subject":"What's cooking in git.git (Dec 2009, #02; Sat, 05)","startedAt":"2009-12-06T08:17:54Z","lastAt":"2009-12-08T05:58:22Z","messageCount":5,"participants":["Junio C Hamano","Martin Storsjö","Shawn O. Pearce","Tay Ray Chuan"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"129322","messageId":"7vpr6siki5.fsf@alter.siamese.dyndns.org","threadId":"21877","inReplyTo":null,"subject":"What's cooking in git.git (Dec 2009, #02; Sat, 05)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-12-06T08:17:54Z","receivedAt":"2009-12-06T08:17:54Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here are the topics that have been cooking.  Commits prefixed with '-' are\nonly in 'pu' while commits prefixed with '+' are in 'next'.  The ones\nmarked with '.' do not appear in any of the integration branches, but I am\nstill holding onto them.\n\nIn 1.7.0, we plan to correct handful of warts in the interfaces everybody\nagrees that they were mistakes.  The resulting system may not be strictly\nbackward compatible.  Currently planned changes are:\n\n * refuse push to update the checked out branch in a non-bare repo by\n   default\n\n   Make \"git push\" into a repository to update the branch that is checked\n   out fail by default.  You can countermand this default by setting a\n   configuration variable in the receiving repository.\n\n   http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007\n\n * refuse push to delete the current branch by default\n\n   Make \"git push $there :$killed\" to delete the branch that is pointed at\n   by its HEAD fail by default.  You can countermand this default by\n   setting a configuration variable in the receiving repository.\n\n   http://thread.gmane.org/gmane.comp.version-control.git/108862/focus=108936\n\n * \"git send-email\" won't make deep threads by default\n\n   Many people said that by default when sending more than 2 patches the\n   threading git-send-email makes by default is hard to read, and they\n   prefer the default be one cover letter and each patch as a direct\n   follow-up to the cover letter.  You can countermand this by setting a\n   configuration variable.\n\n   http://article.gmane.org/gmane.comp.version-control.git/109790\n\n * \"git status\" won't be \"git-commit --dry-run\" anymore\n\n   http://thread.gmane.org/gmane.comp.version-control.git/125989/focus=125993\n\n * \"git diff -w --exit-code\" will exit success if only differences it\n   found are whitespace changes that are stripped away from the output.\n\n   http://thread.gmane.org/gmane.comp.version-control.git/119731/focus=119751\n\n * \"git diff -w/-b\" won't even produce \"diff --git\" header when all changes\n   are about whitespaces.\n\n   http://thread.gmane.org/gmane.comp.version-control.git/133256\n\n--------------------------------------------------\n[New Topics]\n\nNote: Ilari's vcs-helper series hasn't been queued yet, as its first round\ngenerated a healthy amount of discussion and he made it clear that the\nsecond round is being prepared, addressing the comments given on the list.\nHopefully trivial coding style issues in the first round will also be\nfixed (e.g. keyword \"if\" lacked a SP after it before opening parenthesis\nof the condition) in the second round.\n\n* jn/maint-pull-rebase-error-message (2009-11-27) 1 commit.\n  (merged to 'next' on 2009-12-03 at 2ced03c)\n + pull: clarify advice for the unconfigured error case\n\nReplaces old 'jn/rfc-pull-rebase-error-message' topic.\n\n* fc/opt-quiet-gc-reset (2009-12-02) 1 commit\n - General --quiet improvements\n\n* mv/commit-date (2009-12-03) 2 commits\n - Document date formats accepted by parse_date()\n - builtin-commit: add --date option\n\n* mh/rebase-fixup (2009-12-05) 4 commits\n - [squash to Add a command \"fix\"] Avoid \"\\(alternatives\\|choices\\)\" in sed script\n - Add a command \"fix\" to rebase --interactive.\n - t3404: set a couple more tags in the original repository\n - t3404: Better document the original repository layout\n\n--------------------------------------------------\n[Stalled]\n\n* je/send-email-no-subject (2009-08-05) 1 commit.\n  (merged to 'next' on 2009-10-11 at 1b99c56)\n + send-email: confirm on empty mail subjects\n\nThe existing tests cover the positive case (i.e. as long as the user says\n\"yes\" to the \"do you really want to send this message that lacks subject\",\nthe message is sent) of this feature, but the feature itself needs its own\ntest to verify the negative case (i.e. does it correctly stop if the user\nsays \"no\"?)\n\n* jc/checkout-merge-base (2009-11-20) 2 commits\n - \"rebase --onto A...B\" replays history on the merge base between A and B\n - \"checkout A...B\" switches to the merge base between A and B\n\nI've been using the first one for a while myself but do not see many users\nwant this (yet); the new feature is not urgent anyway.\n\n* jh/notes (2009-12-02) 11 commits\n - Refactor notes concatenation into a flexible interface for combining notes\n - Notes API: Allow multiple concurrent notes trees with new struct notes_tree\n - Notes API: for_each_note(): Traverse the entire notes tree with a callback\n - Notes API: get_note(): Return the note annotating the given object\n - Notes API: add_note(): Add note objects to the internal notes tree structure\n - Notes API: init_notes(): Initialize the notes tree from the given notes ref\n - Notes API: get_commit_notes() -> format_note() + remove the commit restriction\n - Minor style fixes to notes.c\n - Add more testcases to test fast-import of notes\n - Rename t9301 to t9350, to make room for more fast-import tests\n - fast-import: Proper notes tree manipulation\n\nRerolled (waiting for Acks).\n\n* tr/maint-merge-ours-clarification (2009-11-15) 1 commit\n  (merged to 'next' on 2009-11-21 at fadaf7b)\n + rebase: refuse to rebase with -s ours\n\nI do not think we reached a concensus for solving conflicts between \"give\nthem rope\" and \"protect users from clearly meaningless combinations\".  The\nauthor obviously is for the latter (and I am inclined to agree); Dscho\nseems to think otherwise.\n\n* jc/fix-tree-walk (2009-10-22) 8 commits\n  (merged to 'next' on 2009-10-22 at 10c0c8f)\n + Revert failed attempt since 353c5ee\n + read-tree --debug-unpack\n  (merged to 'next' on 2009-10-11 at 0b058e2)\n + unpack-trees.c: look ahead in the index\n + unpack-trees.c: prepare for looking ahead in the index\n + Aggressive three-way merge: fix D/F case\n + traverse_trees(): handle D/F conflict case sanely\n + more D/F conflict tests\n + tests: move convenience regexp to match object names to test-lib.sh\n\nThis has some stupid bugs and reverted from 'next' until I can fix it, but\nthe \"temporarily\" turned out to be very loooong.  Sigh.  We won't have a\nproper fix in 1.6.6.\n\n* jc/grep-full-tree (2009-11-24) 1 commit.\n - grep: --full-tree\n\nThe interaction with this option and pathspecs need to be worked out\nbetter.  I _think_ \"grep --full-tree -e pattern -- '*.h'\" should find from\nall the header files in the tree, for example.\n\n--------------------------------------------------\n[Cooking]\n\n* sr/gfi-options (2009-12-04) 7 commits\n - fast-import: add (non-)relative-marks feature\n - fast-import: allow for multiple --import-marks= arguments\n - fast-import: test the new option command\n - fast-import: add option command\n - fast-import: add feature command\n - fast-import: put marks reading in its own function\n - fast-import: put option parsing code in separate functions\n\nRerolled.\n\n* ap/merge-backend-opts (2008-07-18) 6 commits\n - Document that merge strategies can now take their own options\n - Extend merge-subtree tests to test -Xsubtree=dir.\n - Make \"subtree\" part more orthogonal to the rest of merge-recursive.\n - Teach git-pull to pass -X<option> to git-merge\n - git merge -X<option>\n - git-merge-file --ours, --theirs\n\n\"git pull\" patch needs sq-then-eval fix to protect it from $IFS\nbut otherwise seemed good.\n\n* mo/bin-wrappers (2009-12-02) 3 commits\n - INSTALL: document a simpler way to run uninstalled builds\n - run test suite without dashed git-commands in PATH\n - build dashless \"bin-wrappers\" directory similar to installed bindir\n\nRerolled.\n\n* tr/http-updates (2009-12-01) 3 commits\n - Allow curl to rewind the RPC read buffer\n - Add an option for using any HTTP authentication scheme, not only basic\n - http: maintain curl sessions\n\nThere was a discussion on a better structure not to require rewinding in\nthe first place?  I didn't follow it closely...\n\n* jc/diff-whitespace-prepare (2009-11-28) 2 commits\n - diff: flip the default diff.bwoutputonly to true\n - diff: optionally allow traditional \"-b/-w affects only output\" semantics\n (this branch uses gb/1.7.0-diff-whitespace-only-output and jc/1.7.0-diff-whitespace-only-status; is used by jc/1.7.0-diff-whitespace-prepare.)\n\nThis is to redo the two -b/-w semantic changes to prepare the migration of\nexisting users before 1.7.0 happens.\n\n* sr/vcs-helper (2009-12-04) 13 commits\n  (merged to 'next' on 2009-12-03 at e45b562)\n + builtin-push: don't access freed transport->url\n  (merged to 'next' on 2009-11-27 at 83268ab)\n + Add Python support library for remote helpers\n + Basic build infrastructure for Python scripts\n + Allow helpers to report in \"list\" command that the ref is unchanged\n + Fix various memory leaks in transport-helper.c\n + Allow helper to map private ref names into normal names\n + Add support for \"import\" helper command\n + Allow specifying the remote helper in the url\n + Add a config option for remotes to specify a foreign vcs\n + Allow fetch to modify refs\n + Use a function to determine whether a remote is valid\n + Allow programs to not depend on remotes having urls\n + Fix memory leak in helper method for disconnect\n\nShould be among the first to graduate after 1.6.6 final.\n\n* tr/reset-checkout-patch (2009-11-19) 1 commit.\n  (merged to 'next' on 2009-11-22 at b224950)\n + {checkout,reset} -p: make patch direction configurable\n\nI do not particularly like a configuration like this that changes the\nbehaviour of a command in a drastic way---it will make helping others\nmuch harder.\n\n* nd/sparse (2009-11-25) 20 commits.\n  (merged to 'next' on 2009-11-25 at 71380f5)\n + tests: rename duplicate t1009\n  (merged to 'next' on 2009-11-23 at f712a41)\n + sparse checkout: inhibit empty worktree\n + Add tests for sparse checkout\n + read-tree: add --no-sparse-checkout to disable sparse checkout support\n + unpack-trees(): ignore worktree check outside checkout area\n + unpack_trees(): apply $GIT_DIR/info/sparse-checkout to the final index\n + unpack-trees(): \"enable\" sparse checkout and load $GIT_DIR/info/sparse-checkout\n + unpack-trees.c: generalize verify_* functions\n + unpack-trees(): add CE_WT_REMOVE to remove on worktree alone\n + Introduce \"sparse checkout\"\n + dir.c: export excluded_1() and add_excludes_from_file_1()\n + excluded_1(): support exclude files in index\n + unpack-trees(): carry skip-worktree bit over in merged_entry()\n + Read .gitignore from index if it is skip-worktree\n + Avoid writing to buffer in add_excludes_from_file_1()\n + Teach Git to respect skip-worktree bit (writing part)\n + Teach Git to respect skip-worktree bit (reading part)\n + Introduce \"skip-worktree\" bit in index, teach Git to get/set this bit\n + Add test-index-version\n + update-index: refactor mark_valid() in preparation for new options\n\nThere were some test glitches reported and at least one test seems to \nbe broken in the sense that it is not testing what it is trying to.\nFix-up expected.\n\n--------------------------------------------------\n[For 1.7.0]\n\n* jk/1.7.0-status (2009-12-05) 9 commits.\n  (merged to 'next' on 2009-12-05 at 44dcefd)\n + status -s: obey color.status\n + builtin-commit: refactor short-status code into wt-status.c\n  (merged to 'next' on 2009-11-27 at 91691ec)\n + t7508-status.sh: Add tests for status -s\n + status -s: respect the status.relativePaths option\n  (merged to 'next' on 2009-11-21 at 884bb56)\n + docs: note that status configuration affects only long format\n  (merged to 'next' on 2009-10-11 at 65c8513)\n + commit: support alternate status formats\n + status: add --porcelain output format\n + status: refactor format option parsing\n + status: refactor short-mode printing to its own function\n (this branch uses jc/1.7.0-status.)\n\nGives the --short output format to post 1.7.0 \"git commit --dry-run\" that\nis similar to that of post 1.7.0 \"git status\".\n\nImmediately after 1.6.6 while rebuilding 'next', we may want to reorder a\nfew commits at the tip, as \"docs: affects only long format\" describes a\nlimitation that will disappear soon.\n\n* jc/1.7.0-status (2009-09-05) 4 commits.\n  (merged to 'next' on 2009-10-11 at 9558627)\n + status: typo fix in usage\n + git status: not \"commit --dry-run\" anymore\n + git stat -s: short status output\n + git stat: the beginning of \"status that is not a dry-run of commit\"\n (this branch is used by jk/1.7.0-status.)\n\nWith this, \"git status\" is no longer \"git commit --dry-run\".\n\n* jc/1.7.0-send-email-no-thread-default (2009-08-22) 1 commit.\n  (merged to 'next' on 2009-10-11 at 043acdf)\n + send-email: make --no-chain-reply-to the default\n\nAs the title says.\n\n* jc/1.7.0-push-safety (2009-02-09) 2 commits.\n  (merged to 'next' on 2009-10-11 at 81b8128)\n + Refuse deleting the current branch via push\n + Refuse updating the current branch in a non-bare repository via push\n\n* jc/1.7.0-diff-whitespace-only-status (2009-08-30) 4 commits.\n  (merged to 'next' on 2009-10-11 at 546c74d)\n + diff.c: fix typoes in comments\n + Make test case number unique\n + diff: Rename QUIET internal option to QUICK\n + diff: change semantics of \"ignore whitespace\" options\n (this branch is used by jc/1.7.0-diff-whitespace-prepare and jc/diff-whitespace-prepare.)\n\nThis changes exit code from \"git diff --ignore-whitespace\" and friends\nwhen there is no actual output.  It is a backward incompatible change,\nand jc/diff-whitespace-prepare topic is meant to ease the transition.\n\n* gb/1.7.0-diff-whitespace-only-output (2009-11-19) 1 commit\n  (merged to 'next' on 2009-11-21 at 3375bf4)\n + No diff -b/-w output for all-whitespace changes\n (this branch is used by jc/1.7.0-diff-whitespace-prepare and jc/diff-whitespace-prepare.)\n\nLikewise but for the output of \"diff --git\" headers.\n\n* jc/1.7.0-diff-whitespace-prepare (2009-11-28) 2 commits\n - diff: disable diff.bwoutputonly warning\n - diff: flip the diff.bwoutputonly default to false\n (this branch uses gb/1.7.0-diff-whitespace-only-output, jc/1.7.0-diff-whitespace-only-status and jc/diff-whitespace-prepare.)\n\nAnd this is to actually flip the default and eventually remove the warning.\n\n* ns/1.7.0-send-email-no-chain-reply-to (2009-08-22) 1 commit\n - send-email: make --no-chain-reply-to the default\n\nAnd this is to actually flip the default in 1.7.0.\n\n--------------------------------------------------\n[Reverted from 'next']\n\n* jc/botched-maint-cygwin-count-objects (2009-11-24) 2 commits.\n  (merged to 'next' on 2009-11-25 at 8aa62a0)\n + Revert \"ST_BLOCKS_COUNTS_IN_BLKSIZE to say on-disk size is (st_blksize * st_blocks)\"\n  (merged to 'next' on 2009-11-22 at 4ba5880)\n + ST_BLOCKS_COUNTS_IN_BLKSIZE to say on-disk size is (st_blksize * st_blocks)\n\nThis is a revert of the tip one I merged prematurely to 'next'.  The real\nfix from Ramsay is already in 'master'.\n\n* ks/precompute-completion (2009-11-15) 4 commits.\n  (merged to 'next' on 2009-11-15 at 23cdb96)\n + Revert ks/precompute-completion series\n  (merged to 'next' on 2009-10-28 at cd5177f)\n + completion: ignore custom merge strategies when pre-generating\n  (merged to 'next' on 2009-10-22 at f46a28a)\n + bug: precomputed completion includes scripts sources\n  (merged to 'next' on 2009-10-14 at adf722a)\n + Speedup bash completion loading\n\nReverted out of 'next', to be replaced with jn/faster-completion-startup\ntopic.\n\n--------------------------------------------------\n[I have been too busy to purge these]\n\n* jn/rfc-pull-rebase-error-message (2009-11-12) 1 commit\n . git-pull.sh --rebase: overhaul error handling when no candidates are found\n\nReplaced.\n\n* jc/log-tz (2009-03-03) 1 commit.\n - Allow --date=local --date=other-format to work as expected\n\nMaybe some people care about this.  I dunno.\n\n* jc/1.7.0-no-commit-no-ff-2 (2009-10-22) 1 commit.\n . git-merge: forbid fast-forward and up-to-date when --no-commit is given\n\nThis makes \"git merge --no-commit\" fail when it results in fast-forward or\nup-to-date.  It appears nobody wants to have this, so I dropped it.\n\n* ne/rev-cache (2009-10-19) 7 commits.\n . support for commit grafts, slight change to general mechanism\n . support for path name caching in rev-cache\n . full integration of rev-cache into git, completed test suite\n . administrative functions for rev-cache, start of integration into git\n . support for non-commit object caching in rev-cache\n . basic revision cache system, no integration or features\n . man page and technical discussion for rev-cache\n\nThe author indicated that there is another round coming.  Does not seem to\npass the tests when merged to 'pu', so it has been ejected for now.\n\n* pb/gitweb-no-project-list (2009-11-06) 3 commits.\n . gitweb: Polish the content tags support\n . gitweb: Support for no project list on gitweb front page\n . gitweb: Refactor project list routines\n\nI picked these up but didn't queue as Warthog9's comments made certain\namount of sense to me.\n"},{"id":"129333","messageId":"alpine.DEB.2.00.0912061738580.5582@cone.home.martin.st","threadId":"21877","inReplyTo":"7vpr6siki5.fsf@alter.siamese.dyndns.org","subject":"Re: What's cooking in git.git (Dec 2009, #02; Sat, 05)","fromName":"Martin Storsjö","fromEmail":"martin@martin.st","sentAt":"2009-12-06T15:59:06Z","receivedAt":"2009-12-06T15:59:06Z","isPatch":false,"sender":{"key":"martin@martin.st","avatar":"https://avatars.githubusercontent.com/u/69727?v=4"},"body":"On Sun, 6 Dec 2009, Junio C Hamano wrote:\n\n> [Cooking]\n> \n> * tr/http-updates (2009-12-01) 3 commits\n>  - Allow curl to rewind the RPC read buffer\n>  - Add an option for using any HTTP authentication scheme, not only basic\n>  - http: maintain curl sessions\n> \n> There was a discussion on a better structure not to require rewinding in\n> the first place?  I didn't follow it closely...\n\nI think the conclusion is: Rewinding support isn't strictly necessary, \nthere's a number of mechanisms in both git and curl that should make sure \nthat those cases shouldn't surface. A few of them in curl have an \nunfortunate conincidence of bugs up until the latest version, though, \nleaving much fewer mechanisms in place to avoid this.\n\nSince that patch is quite non-intrusive I think it's a good safeguard, \nthough. What do you think, Tay, keep it or leave it?\n\n// Martin\n"},{"id":"129426","messageId":"20091207153736.GC17173@spearce.org","threadId":"21877","inReplyTo":"alpine.DEB.2.00.0912061738580.5582@cone.home.martin.st","subject":"Re: What's cooking in git.git (Dec 2009, #02; Sat, 05)","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2009-12-07T15:37:36Z","receivedAt":"2009-12-07T15:37:36Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Martin Storsj? <martin@martin.st> wrote:\n> On Sun, 6 Dec 2009, Junio C Hamano wrote:\n> > \n> > * tr/http-updates (2009-12-01) 3 commits\n> >  - Allow curl to rewind the RPC read buffer\n> >  - Add an option for using any HTTP authentication scheme, not only basic\n> >  - http: maintain curl sessions\n> > \n> > There was a discussion on a better structure not to require rewinding in\n> > the first place?  I didn't follow it closely...\n> \n> I think the conclusion is: Rewinding support isn't strictly necessary, \n> there's a number of mechanisms in both git and curl that should make sure \n> that those cases shouldn't surface. A few of them in curl have an \n> unfortunate conincidence of bugs up until the latest version, though, \n> leaving much fewer mechanisms in place to avoid this.\n> \n> Since that patch is quite non-intrusive I think it's a good safeguard, \n> though. What do you think, Tay, keep it or leave it?\n\nI think the conclusion of the thread was that what you have queued\nin tr/http-updates is OK as-is.  The patch to grow the postbuffer\nto store the entire request wasn't a good idea and got dropped.\n\n-- \nShawn.\n"},{"id":"129443","messageId":"7v7hsy35vc.fsf@alter.siamese.dyndns.org","threadId":"21877","inReplyTo":"20091207153736.GC17173@spearce.org","subject":"Re: What's cooking in git.git (Dec 2009, #02; Sat, 05)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-12-07T20:07:35Z","receivedAt":"2009-12-07T20:07:35Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Shawn O. Pearce\" <spearce@spearce.org> writes:\n\n> Martin Storsj? <martin@martin.st> wrote:\n>> On Sun, 6 Dec 2009, Junio C Hamano wrote:\n>> > \n>> > * tr/http-updates (2009-12-01) 3 commits\n>> >  - Allow curl to rewind the RPC read buffer\n>> >  - Add an option for using any HTTP authentication scheme, not only basic\n>> >  - http: maintain curl sessions\n>> > \n>> > There was a discussion on a better structure not to require rewinding in\n>> > the first place?  I didn't follow it closely...\n>> \n>> I think the conclusion is: Rewinding support isn't strictly necessary, \n>> there's a number of mechanisms in both git and curl that should make sure \n>> that those cases shouldn't surface. A few of them in curl have an \n>> unfortunate conincidence of bugs up until the latest version, though, \n>> leaving much fewer mechanisms in place to avoid this.\n>> \n>> Since that patch is quite non-intrusive I think it's a good safeguard, \n>> though. What do you think, Tay, keep it or leave it?\n>\n> I think the conclusion of the thread was that what you have queued\n> in tr/http-updates is OK as-is.  The patch to grow the postbuffer\n> to store the entire request wasn't a good idea and got dropped.\n\nThanks.\n"},{"id":"129483","messageId":"be6fef0d0912072158g1334aaf0s46299d833f694f1d@mail.gmail.com","threadId":"21877","inReplyTo":"20091207153736.GC17173@spearce.org","subject":"Re: What's cooking in git.git (Dec 2009, #02; Sat, 05)","fromName":"Tay Ray Chuan","fromEmail":"rctay89@gmail.com","sentAt":"2009-12-08T05:58:22Z","receivedAt":"2009-12-08T05:58:22Z","isPatch":false,"sender":{"key":"rctay89@gmail.com","avatar":"https://avatars.githubusercontent.com/u/61553?v=4"},"body":"Hi,\n\nOn Mon, Dec 7, 2009 at 11:37 PM, Shawn O. Pearce <spearce@spearce.org> wrote:\n> Martin Storsj? <martin@martin.st> wrote:\n>> On Sun, 6 Dec 2009, Junio C Hamano wrote:\n>> >\n>> > * tr/http-updates (2009-12-01) 3 commits\n>> >  - Allow curl to rewind the RPC read buffer\n>> >  - Add an option for using any HTTP authentication scheme, not only basic\n>> >  - http: maintain curl sessions\n>> >\n>> > There was a discussion on a better structure not to require rewinding in\n>> > the first place?  I didn't follow it closely...\n>>\n>> I think the conclusion is: Rewinding support isn't strictly necessary,\n>> there's a number of mechanisms in both git and curl that should make sure\n>> that those cases shouldn't surface. A few of them in curl have an\n>> unfortunate conincidence of bugs up until the latest version, though,\n>> leaving much fewer mechanisms in place to avoid this.\n>>\n>> Since that patch is quite non-intrusive I think it's a good safeguard,\n>> though. What do you think, Tay, keep it or leave it?\n>\n> I think the conclusion of the thread was that what you have queued\n> in tr/http-updates is OK as-is.  The patch to grow the postbuffer\n> to store the entire request wasn't a good idea and got dropped.\n\nMartin, sorry the late reply. I agree with Shawn. Perhaps we could\nrelook at rewinding-to-any-position when restarting the rpc client\n(eg. git-send-pack) has been implemented.\n\n-- \nCheers,\nRay Chuan\n"}]}