All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: jonhud <jon@huddler-inc.com>
Cc: git@vger.kernel.org
Subject: Re: How do I see all of my changes on a branch?
Date: Tue, 13 Oct 2009 13:23:00 -0700	[thread overview]
Message-ID: <20091013202300.GC9261@spearce.org> (raw)
In-Reply-To: <25879435.post@talk.nabble.com>

jonhud <jon@huddler-inc.com> wrote:
> We are using github (but that's more or less irrelevant, since I'm just
> running git 1.6 locally on Ubuntu). Some time ago, I created a new branch
> (release.2.2) and pushed it out to the remote repository. All the digging
> through log, gitk, etc. has not made it possible for me to figure out the
> commit (or point in time) at which I cut the branch. 

git merge-base release2.2 HEAD

Which really lets you do:

  git diff $(git merge-base release.2.2 HEAD) HEAD

Which is the long form of:

  git diff release-2.2...HEAD

(diff triple dot operator does the merge base computation for you).
 
-- 
Shawn.

  reply	other threads:[~2009-10-13 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 19:40 How do I see all of my changes on a branch? jonhud
2009-10-13 20:23 ` Shawn O. Pearce [this message]
2009-10-28 12:08 ` Tim Mazid

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=20091013202300.GC9261@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=jon@huddler-inc.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.