git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Seth Falcon <sethfalcon@gmail.com>,
	git@vger.kernel.org
Subject: Re: Change in git-svn dcommit semantics?
Date: Tue, 19 Dec 2006 17:17:17 -0800	[thread overview]
Message-ID: <7v3b7bnz6q.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <C2881A17-27F7-467C-B353-189BB7DBFD1E@silverinsanity.com> (Brian Gernhardt's message of "Tue, 19 Dec 2006 19:38:58 -0500")

Brian Gernhardt <benji@silverinsanity.com> writes:

> And is there an easier way to find these things than "git rev-list
> HEAD | git diff-tree -r -s --stdin -SCOLLISION | xargs git show"?  I
> cobbled that together from poking around inside gitk (which mostly
> works in OS X, but has some issues that make me prefer the command
> line).

I typically do:

	git log --full-diff -p -SCOLLISION

The --full-diff option helps because it shows the diff for other
files (that do not have different number of substring COLLISION
in the pre and postimage) in the same commit as well.


  parent reply	other threads:[~2006-12-20  1:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 21:12 Change in git-svn dcommit semantics? Seth Falcon
2006-12-19 22:09 ` Eric Wong
2006-12-20  3:05   ` Seth Falcon
2006-12-19 23:02 ` Brian Gernhardt
2006-12-19 23:57   ` Johannes Schindelin
2006-12-20  0:38     ` Brian Gernhardt
2006-12-20  0:52       ` Jakub Narebski
2006-12-20  1:17       ` Junio C Hamano [this message]
2006-12-20 11:38         ` Jakub Narebski
2006-12-20 11:47           ` Brian Gernhardt
2006-12-20 11:57             ` Jeff King
2006-12-22 14:09               ` Brian Gernhardt
2006-12-20  3:07   ` Seth Falcon

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7v3b7bnz6q.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=benji@silverinsanity.com \
    --cc=git@vger.kernel.org \
    --cc=sethfalcon@gmail.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).