git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: [PATCH 0/9] Fix oversimplified optimization for add_cache_entry().
Date: Sat, 25 Jun 2005 02:16:23 -0700	[thread overview]
Message-ID: <7vmzpe4x08.fsf_-_@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vaclf6tw7.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 24 Jun 2005 19:40:40 -0700")

>>>>> "JCH" == Junio C Hamano <junkio@cox.net> writes:

>>>>> "LT" == Linus Torvalds <torvalds@osdl.org> writes:
LT> I really don't want to do this. 
LT> Can you fix the "optimized" one instead?

JCH> Will do.

I have this list which logically consists of three sets.  I am
using the new "git rebase" to maintain it and your not taking my
patch stream gave me a good opportunity to test it ;-).

  [PATCH 1/9] [RFC] fix date parsing for GIT raw commit timestamp format.
  [PATCH 2/9] git-commit-script: get commit message from an existing one.
  [PATCH 3/9] git-cherry: find commits not merged upstream.
  [PATCH 4/9] git-rebase-script: rebase local commits to new upstream head.

These four are updated "git rebase" I've written while on-road
without knowing about your git-patch-id; the updated one uses
git-patch-id to identify which are merged and which are not.

To carry earlier commit datetime forward, date.c needs to be
fixed (PATCH 1/9, which I sent you separately Friday), and
enhancing git-commit-script to be able to specify an existing
commit to slurp the commit message (and author & date
information) was necessary (well, not strictly necessary, but
that is the way I am used to, which is stolen from JIT), which
is PATCH 2/9.  PATCH 3/9 and PATCH 4/9 use git-patch-id to
implement the cherrypick/rebase.

  [PATCH 5/9] Add more tests for read-tree --emu23.
  [PATCH 6/9] git-merge-one-file-script: do not misinterpret rm failure
  [PATCH 7/9] Fix oversimplified optimization for add_cache_entry().

These three are reworked D/F conflict fix.  PATCH 5/9 is the
same demonstration of what is broken in the current code.  The
problem fixed by PATCH 6/9 was discovered while I was trying out
the fixes.  PATCH 7/9 teaches your "optimized" has_file/has_dir
implementation to honor stages while they operate.

  [PATCH 8/9] http-pull: documentation updates.
  [PATCH 9/9] Add a bit of developer documentation to pull.h

These are resend.


  reply	other threads:[~2005-06-25  9:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 23:20 [PATCH 0/2] D/F conflicts fixes Junio C Hamano
2005-06-23 23:25 ` [PATCH 1/2] Add more tests for read-tree --emu23 Junio C Hamano
2005-06-24 23:40 ` [PATCH 2/2] Fix oversimplified optimization for add_cache_entry() Junio C Hamano
2005-06-25  0:57   ` Linus Torvalds
2005-06-25  2:40     ` Junio C Hamano
2005-06-25  9:16       ` Junio C Hamano [this message]
2005-06-25  9:21         ` [PATCH 1/9] fix date parsing for GIT raw commit timestamp format Junio C Hamano
2005-06-25  9:22         ` [PATCH 2/9] git-commit-script: get commit message from an existing one Junio C Hamano
2005-06-25  9:22         ` [PATCH 3/9] git-cherry: find commits not merged upstream Junio C Hamano
2005-06-25  9:23         ` [PATCH 4/9] git-rebase-script: rebase local commits to new upstream head Junio C Hamano
2005-06-25  9:24         ` [PATCH 5/9] Add more tests for read-tree --emu23 Junio C Hamano
2005-06-25  9:24         ` [PATCH 6/9] git-merge-one-file-script: do not misinterpret rm failure Junio C Hamano
2005-06-25  9:25         ` [PATCH 7/9] Fix oversimplified optimization for add_cache_entry() Junio C Hamano
2005-06-25  9:25         ` [PATCH 8/9] http-pull: documentation updates Junio C Hamano
2005-06-25  9:26         ` [PATCH 9/9] Add a bit of developer documentation to pull.h Junio C Hamano
2005-06-26  1:02         ` [RFD] consider "git" wrapper semi-Porcelain Junio C Hamano
2005-06-26  1:21           ` Linus Torvalds
2005-06-26 12:02             ` Junio C Hamano
2005-06-26 12:36               ` Martijn Kuipers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vmzpe4x08.fsf_-_@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).