From: Linus Torvalds <torvalds@linux-foundation.org>
To: Bill Lear <rael@zopyra.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Error converting from 1.4.4.1 to 1.5.0?
Date: Wed, 14 Feb 2007 15:03:19 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0702141447290.20368@woody.linux-foundation.org> (raw)
In-Reply-To: <17875.33204.413186.355557@lisa.zopyra.com>
On Wed, 14 Feb 2007, Bill Lear wrote:
>
> WAAAAAIAMINIT ... I think I see it:
>
> % perl -pi -e 's/.*\$Id.*//sx' $(xgrep -l '[$]Id')
>
> Could I have corrupted the pack file? I'll bet $50 I did:
Heh.
I'm relieved git is off the hook, although I think we should still look at
that SIGSEGV. We might well have some situation where we react badly do a
corrupt pack (most likely, by having one of the object parsing routines
return NULL, and then we follow that NULL pointer rather than saying "bad
object").
> % [yet another clone]
> % xgrep -l '[$]Id'
> ./.git/objects/pack/pack-23d1a9af78b4b78d1f3750cf70f83cb91a20ba64.pack
This is just one reason I don't ever use 'find' on my source tree. I long
ago used to do
find . -name '*.c' | xargs grep ...
etc, but especially with git I have almost totally stopped using "xargs
grep" entirely - to the point where I actually end up importing tar-files
into new git archives just because I'm so used to "git grep".
So I would suggest that in order to avoid this in the future, you teach
your fingers to say "git grep" instead of "xgrep"., which I assume is just
some local alias of yours for "find .. | xargs grep"?
"git grep" really works wonderfully well, and you could have just done
perl -pi -e 's/.*\$Id.*//sx' $(git grep -l '[$]Id')
instead.
("git grep" is much nicer than "xargs grep" in many other ways too. You
can ask it to limit itself to a certain pattern of filenames etc by doing
git grep -l '[$]Id' -- 'net/*.[ch]'
as long as you realize that the name pattern for git grep considers '*' to
act like '**' does for some shells - ie it globs against '/'too, so the
above will find any C and header files under the net/ directory, however
deep they are.. And you can ask it to grep in just a certain revision etc
too).
Once you get used to "git grep", I bet you'll forget all about "xgrep",
and won't have to worry about going into the .git/ directory by mistake
any more.
There are other tricks you can do, but they are somewhat inconvenient.
They range from making ".git" a symlink to somewhere else (to stop
"find" from following it), and in your case, since you apparently already
have an "xgrep" alias for this, you could just teach your "find" thing to
do something like what we do in the kernel Makefile:
RCS_FIND_IGNORE := \( -name SCCS -o -name BitKeeper -o -name .svn -o -name CVS -o -name .pc -o -name .hg -o -name .git \) -prune -o
and then we use
find . $(RCS_FIND_IGNORE) ...
which knows to ignore ".git" directories along with all the other
SCCS/CVS/SVN/BK/etc directories.
Linus
next prev parent reply other threads:[~2007-02-14 23:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 16:12 Error converting from 1.4.4.1 to 1.5.0? Bill Lear
2007-02-14 17:07 ` Bill Lear
2007-02-14 17:15 ` Junio C Hamano
2007-02-14 17:20 ` Bill Lear
2007-02-14 17:45 ` Junio C Hamano
2007-02-14 20:49 ` Bill Lear
2007-02-14 20:58 ` Bill Lear
2007-02-14 21:19 ` Linus Torvalds
2007-02-14 21:40 ` Bill Lear
2007-02-14 21:47 ` Junio C Hamano
2007-02-14 21:52 ` Junio C Hamano
2007-02-14 22:04 ` Johannes Schindelin
2007-02-14 22:13 ` Junio C Hamano
2007-02-14 22:32 ` Johannes Schindelin
2007-02-15 0:41 ` Jakub Narebski
2007-02-15 0:54 ` Olivier Galibert
2007-02-15 1:36 ` Johannes Schindelin
2007-02-14 22:02 ` Johannes Schindelin
2007-02-14 22:27 ` Nicolas Pitre
2007-02-14 22:41 ` Bill Lear
2007-02-15 1:18 ` OT: data destruction classics (was: Re: Error converting from 1.4.4.1 to 1.5.0?) Simon 'corecode' Schubert
2007-02-15 2:13 ` Shawn O. Pearce
2007-02-15 2:51 ` Linus Torvalds
2007-02-15 10:24 ` Johannes Schindelin
2007-02-15 13:13 ` Michael K. Edwards
2007-02-15 11:58 ` Bill Lear
2007-02-15 9:13 ` Andy Parkins
2007-02-15 14:30 ` Mark Wooding
2007-02-14 23:24 ` Error converting from 1.4.4.1 to 1.5.0? Linus Torvalds
2007-02-14 23:03 ` Linus Torvalds [this message]
2007-02-15 8:40 ` Uwe Kleine-König
2007-02-14 21:12 ` Junio C Hamano
2007-02-14 21:18 ` Bill Lear
2007-02-14 21:14 ` Nicolas Pitre
2007-02-14 21:32 ` Junio C Hamano
2007-02-14 18:19 ` Linus Torvalds
2007-02-14 18:42 ` Linus Torvalds
2007-02-14 21:13 ` Bill Lear
2007-02-14 21:35 ` Linus Torvalds
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=Pine.LNX.4.64.0702141447290.20368@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=rael@zopyra.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 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).