Re: [PATCH and RFC] gitweb: Remove --full-history from git_history

From: Junio C Hamano <>
Date: 2006-08-10 07:42:13
Fredrik Kuivinen <> writes:

> I don't think it was dropped in favor --full-history.


The --full-history option is about merge simplification and has
nothing to do with renames.

The thing is, your patch, while I very much liked the direction
it was taking us, was so intrusive that it scared the h*ck out
of me ;-).

>> What is needed by gitweb is for git-rev-list to not only follow revisions
>> of file contents across renames, and return more revisions, 
> Note that it is not enough to only return more revisions.
> For example, consider the commits (newest commit first)
> A: Rename "bar" to "foo"
> B: No changes to "bar"
> C: No changes to "bar", delete "foo"
> <more commits here>
> Then you want "git-rev-list --renames A -- foo" to return A,... not A,C,...

Yes.  For this "following renames for a single file" example, we
should not extend the pathspec which originally starts out as
"foo" to _include_ "bar"; instead it should _replace_, and after
that point we should not care about "foo".

This was another reason I shied away from your patch back then.
We would need to think about interactions between this pathspec
for a single file (which should be switched) and pathspecs for
directories ("more useful form of usage than single file", as
Linus would put it).

I have this vague feeling, without revisiting the code to make
an informed argument, that it might be cleaner and with less
impact (read: smaller chance to break the "directories" usage)
if we special case "follow a single file" case.  I dunno.

Also I was not sure how well your pathspec switching worked
across forks and merges.

                            M bar
          /                         \
 A bar   /    R bar->foo  M foo      \     M foo

Suppose we are at 8 and start digging for the history of "foo".
Our pathspec starts out as "foo" at 8 and stays so until we hit
6.  If the lower branch renamed bar->foo while the upper didn't,
and merge-recursive merged them correctly at 6, we would use
"foo" as pathspec while on the lower branch while traversing 6,
3 and 2 (at that point we switch to "bar").  On the upper
branch, we switch pathspec to "bar" while traversing 6, 5, 4.
When we hit 1, pathspec of both of its children (2 and 4) happen
to match in this example.  But what would we do if for some
reason they didn't?  Do we care?  Is that die("an internal
error")?  I did not have a good anser to that question, and I
still don't.

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at
Received on Thu Aug 10 07:42:55 2006

This archive was generated by hypermail 2.1.8 : 2006-08-10 07:43:31 EST