threads / discuss / 9187

git log and --first-parent

Subject: git log and --first-parent

## tl;dr

2 messages between Jul 23, 2007 and Jul 26, 2007.

replies: 1people: 1as markdown or json

Robin Rosenberg· Jul 23, 2007, 23:05 UTC · lore

I'm puzzled over the behavior of --first-parent. The documentations seems to imply that only the first parent is followed, but when a filter is applied it seems (just guessing) that the "first" parent is selected *after* filtering, a behaviour that I feel does not match the documentation.

Should the first-parent filter be applied first.
Example:
	git log --first-parent --pretty=format: --name-only v1.5.2|grep ^var.c|wc -l
counts four commits where var.c was changed, while
	git log --first-parent --pretty=format: --name-only v1.5.2 -- var.c |wc -l
gives me 23. 
-- robin
Robin Rosenberg· Jul 26, 2007, 20:30 UTC · re: Robin Rosenberg · lore

Re: git log and --first-parent

tisdag 24 juli 2007 skrev Robin Rosenberg:
Show 19 quoted lines
> 
> I'm puzzled over the behavior of --first-parent. The documentations seems to imply
> that only the first parent is followed, but when a filter is applied it seems (just guessing)
> that the "first" parent is selected *after* filtering, a behaviour that I feel does not match
> the documentation.
> 
> Should the first-parent filter be applied first.
> 
> Example:
> 
> 	git log --first-parent --pretty=format: --name-only v1.5.2|grep ^var.c|wc -l
> 
> counts four commits where var.c was changed, while
> 
> 	git log --first-parent --pretty=format: --name-only v1.5.2 -- var.c |wc -l
> 
> gives me 23. 
> 
> -- robin

Now, I also realize fast-forwards means --first-parent may not be as useful as I first hoped.

-- robin

← back to recent threads