Git Log and History Simplification

Git Log and History Simplification

[Dinesh Subramani]

I am using the below command :

git log --stat --decorate=full --since=<date>

Can you please let me know if the above command will list all the
commits and would not skip any of the commits due to History
Simplification. Any help would be very useful.

Regards,
Dinesh

Re: Git Log and History Simplification

[Nguyen Thai Ngoc Duy]

On Mon, Dec 17, 2012 at 6:33 PM, Dinesh Subramani
<dinesh.subramani@gmail.com> wrote:
> I am using the below command :
>
> git log --stat --decorate=full --since=<date>
>
> Can you please let me know if the above command will list all the
> commits and would not skip any of the commits due to History
> Simplification. Any help would be very useful.

If my memory is still functioning, history simplification only takes
place when you specify pathspec. The above command does not have
pathspec, so no history simplification.
-- 
Duy

Re: Git Log and History Simplification

[Tomas Carnecky]

On Mon, 17 Dec 2012 17:03:09 +0530, Dinesh Subramani <dinesh.subramani@gmail.com> wrote:
> I am using the below command :
> 
> git log --stat --decorate=full --since=<date>
> 
> Can you please let me know if the above command will list all the
> commits and would not skip any of the commits due to History
> Simplification. Any help would be very useful.

The way I understand the man page, to disable history simplification you have
to use --full-history --sparse.

Re: Git Log and History Simplification

[Junio C Hamano]

Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:

> On Mon, Dec 17, 2012 at 6:33 PM, Dinesh Subramani
> <dinesh.subramani@gmail.com> wrote:
>> I am using the below command :
>>
>> git log --stat --decorate=full --since=<date>
>>
>> Can you please let me know if the above command will list all the
>> commits and would not skip any of the commits due to History
>> Simplification. Any help would be very useful.
>
> If my memory is still functioning, history simplification only takes
> place when you specify pathspec. The above command does not have
> pathspec, so no history simplification.

Think of the pathspec limiting as asking to choose commits by one
criteria (i.e. touches paths in a way that matters in the result),
like any other commit limiting criteria like "--grep" (i.e. asks to
choose commits that has the given string in its message).

With something like --author or --grep, we would need to look at
each individual commmit to decide if it matches the criteria.  With
pathspec, when we look at a single-parent commit, we inspect it to
decide if it matches the criteria of touching the specified paths.

When we are looking at a merge commit, however, if one of the
parents match the result at all the paths that match the given
pathspec, we know any and all commits on the other side branches do
not matter in the result, hence we can omit them by not even having
to follow that parent ancestry.

If you mention --full-history in your answer, it will be perfect ;-)