From: Brian Gernhardt <benji@silverinsanity.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Seth Falcon <sethfalcon@gmail.com>, git@vger.kernel.org
Subject: Re: Change in git-svn dcommit semantics?
Date: Tue, 19 Dec 2006 19:38:58 -0500 [thread overview]
Message-ID: <C2881A17-27F7-467C-B353-189BB7DBFD1E@silverinsanity.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0612200053550.19693@wbgn013.biozentrum.uni-wuerzburg.de>
On Dec 19, 2006, at 6:57 PM, Johannes Schindelin wrote:
>> Mine also has a few variables like "COLLISION_CHECK=paranoid" and
>> my own
>> prefix.
>
> Just to wake sleeping tigers: have you done a "grep COLLISION_CHECK *"
> recently (where recently means any date after May 3rd, 2005)?
Oh, well, that's cute. It's a configuration option that doesn't
touch any code at all... Not that I really cared about the check, I
just thought it was a nice paranoid thing to activate and I like a
certain amount of paranoia in my SCMs. But maybe the description
should be removed from the Makefile then? Or better yet, collision
checking could be put back in?
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).
next prev parent reply other threads:[~2006-12-20 0:39 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 [this message]
2006-12-20 0:52 ` Jakub Narebski
2006-12-20 1:17 ` Junio C Hamano
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=C2881A17-27F7-467C-B353-189BB7DBFD1E@silverinsanity.com \
--to=benji@silverinsanity.com \
--cc=Johannes.Schindelin@gmx.de \
--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).