gitk highlighting commits

gitk highlighting commits

[picca]

Hello

I am using git to follow the wine development. And I wondering if it
is possible to highlight all the commit since my last git pull ?

Indeed there is so many commits that I can not remenber the
last one I red before I did this git pull.

Maybe using the blob date on the disk ?

Have a nice day.

Re: gitk highlighting commits

[Marius Storm-Olsen]

[-- Attachment #1: Type: text/plain, Size: 686 bytes --]

picca said the following on 08.06.2007 08:45:
> Hello
> 
> I am using git to follow the wine development. And I wondering if it
> is possible to highlight all the commit since my last git pull ?
> 
> Indeed there is so many commits that I can not remenber the
> last one I red before I did this git pull.

You _could_ do:
Simply use a tag to mark the HEAD commit before you do the next pull.
     git tag LastReadCommit
(HEAD is implicit on the tag command)
The tag will then be displayed in gitk, so you know where you left 
off. Then, when you're done, simply move the tag to the new HEAD.
     git tag -d LastReadCommit
     git tag LastReadCommit

-- 
.marius


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

Re: gitk highlighting commits

[Shawn O. Pearce]

picca <picca@synchrotron-soleil.Fr> wrote:
> I am using git to follow the wine development. And I wondering if it
> is possible to highlight all the commit since my last git pull ?

If you do it *right after* the pull, you can see those commits that
are new to you with:

	gitk ORIG_HEAD..

ORIG_HEAD is a special name for the commit that you had just before
you pulled.  So you are asking gitk to show you all commits that
are now in your current branch (implied by nothing to the right of
the ..) that were not in your branch before the pull (ORIG_HEAD).
That is the stuff you just pullled.

If its many days later that you want to look at this and you have
done some things that overwrite ORIG_HEAD (git reset; git rebase;
etc.)  then this becomes more difficult.  But you can also do by
time:

  gitk HEAD@{2.days.ago}..

This shows you everything that is new *to you* in the past two days.
Even if the changes were created months ago and just recently were
pulled by you yesterday, they will appear in gitk, because you asked
for *your* history over the past two days, not the project history.

These same tricks also work with git-log of course:

  git log ORIG_HEAD...
  git log HEAD@{2.days.ago}..

You could also take a look at the manual page for git-rev-parse,
there are some more details covered there I think.
 
-- 
Shawn.

Re: gitk highlighting commits

[Jan Hudec]

[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]

On Fri, Jun 08, 2007 at 02:57:39 -0400, Shawn O. Pearce wrote:
> picca <picca@synchrotron-soleil.Fr> wrote:
> > I am using git to follow the wine development. And I wondering if it
> > is possible to highlight all the commit since my last git pull ?
> 
> If you do it *right after* the pull, you can see those commits that
> are new to you with:
> 
> 	gitk ORIG_HEAD..
> 
> ORIG_HEAD is a special name for the commit that you had just before
> you pulled.  So you are asking gitk to show you all commits that
> are now in your current branch (implied by nothing to the right of
> the ..) that were not in your branch before the pull (ORIG_HEAD).
> That is the stuff you just pullled.
> 
> If its many days later that you want to look at this and you have
> done some things that overwrite ORIG_HEAD (git reset; git rebase;
> etc.)  then this becomes more difficult.  But you can also do by
> time:
> 
>   gitk HEAD@{2.days.ago}..

There is actually one ref which only changes in pulls (and fetches) -- the
tracking brach. Therefore:

gitk origin/master@{1}..

(or whatever you pull) is what you want.

> This shows you everything that is new *to you* in the past two days.
> Even if the changes were created months ago and just recently were
> pulled by you yesterday, they will appear in gitk, because you asked
> for *your* history over the past two days, not the project history.
> 
> These same tricks also work with git-log of course:
> 
>   git log ORIG_HEAD...
>   git log HEAD@{2.days.ago}..
> 
> You could also take a look at the manual page for git-rev-parse,
> there are some more details covered there I think.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]