From: "Shawn O. Pearce" <spearce@spearce.org>
To: picca <picca@synchrotron-soleil.Fr>
Cc: git@vger.kernel.org
Subject: Re: gitk highlighting commits
Date: Fri, 8 Jun 2007 02:57:39 -0400 [thread overview]
Message-ID: <20070608065739.GC18521@spearce.org> (raw)
In-Reply-To: <20070608084501.1b66f16a@localhost.localdomain>
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.
next prev parent reply other threads:[~2007-06-08 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 6:45 gitk highlighting commits picca
2007-06-08 6:55 ` Marius Storm-Olsen
2007-06-08 6:57 ` Shawn O. Pearce [this message]
2007-06-08 21:11 ` Jan Hudec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070608065739.GC18521@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=picca@synchrotron-soleil.Fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).