On Wed, Dec 16, 2009 at 04:59:54PM -0700, Elijah Newren <newren@xxxxxxxxx> wrote:
> Did you try it with a 'new' branch in your repository that started at
> the beginning of history rather than at some commit? "git log new"
> and "git log new@{30.years.ago}..new" are not the same for me with
> git-1.6.5.5:
>
> $ git init repo
> $ cd repo
> $ echo content> foo && git add foo && git commit -mone foo
> $ echo more content >> foo && git commit -mtwo foo
> $ git checkout -b new master~1
> $ echo stuff >> foo && git commit -mthree foo
> $ git log new@{30.years.ago}..new
Aah, thanks. Then you can just avoid the warning using
git log $(git reflog show new|sed -n 's/ .*//;$ p')..new
> Are you sure? I'm more inclined to believe he'd like to see all the
> commits that have been added to the "new" branch since he created it
> (which may be the same as what you say, but not necessarily). Of
> course, neither my assumption or yours match what he actually asked
> for (though I think what he asked for isn't possible and is merely an
> means to the end he really wants).
No, I'm not sure about what he thought, but I hope he will clarify. :)
Attachment:
pgpKUskiaMY5C.pgp
Description: PGP signature