From: Linus Torvalds <torvalds@osdl.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Shawn Pearce <spearce@spearce.org>,
Marco Costalba <mcostalba@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Fast access git-rev-list output: some OS knowledge required
Date: Wed, 6 Dec 2006 16:47:54 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612061642440.3542@woody.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0612070025450.28348@wbgn013.biozentrum.uni-wuerzburg.de>
On Thu, 7 Dec 2006, Johannes Schindelin wrote:
>
> Because, depending on what you do, the revision machinery is not
> reentrable. For example, if you filter by filename, the history is
> rewritten in-memory to simulate a history where just that filename was
> tracked, and nothing else. These changes are not cleaned up after calling
> the internal revision machinery.
Well, it really wouldn't be that hard to add a new library interface to
"reset object state". We could fairly trivially either:
- walk all objects in the object hashes and clear all the flags.
- just clear all objects _and_ the hashes.
Yes, it implies a small amount of manual "management", but considering
that the reason it needs to be manual is that the functions simply _need_
the state, is that such a big deal?
next prev parent reply other threads:[~2006-12-07 0:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 19:24 Fast access git-rev-list output: some OS knowledge required Marco Costalba
2006-12-06 19:28 ` Shawn Pearce
2006-12-06 19:34 ` Marco Costalba
2006-12-06 19:42 ` Shawn Pearce
2006-12-06 19:51 ` Shawn Pearce
2006-12-06 20:08 ` Marco Costalba
2006-12-06 20:18 ` Shawn Pearce
2006-12-07 13:25 ` Andreas Ericsson
2006-12-07 14:53 ` Johannes Schindelin
2006-12-07 15:28 ` Andreas Ericsson
2006-12-07 16:01 ` Johannes Schindelin
2006-12-08 18:34 ` Marco Costalba
2006-12-08 20:10 ` Michael K. Edwards
2006-12-09 12:15 ` Marco Costalba
2006-12-06 23:27 ` Johannes Schindelin
2006-12-07 0:47 ` Linus Torvalds [this message]
2006-12-07 6:46 ` Marco Costalba
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=Pine.LNX.4.64.0612061642440.3542@woody.osdl.org \
--to=torvalds@osdl.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.com \
--cc=spearce@spearce.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).