From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: latest update to git-svn blows up for me
Date: 04 Dec 2006 20:19:41 -0800 [thread overview]
Message-ID: <86slfvj7oi.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20061205040844.GA6826@localdomain>
>>>>> "Eric" == Eric Wong <normalperson@yhbt.net> writes:
Eric> Eric Wong <normalperson@yhbt.net> wrote:
>> Same here.. I'm still waiting for it to fetch and will try to reproduce
>> it here.
Eric> Update: Nearly 16k revisions later and I still can't reproduce this on
Eric> my computer.
I still say it was odd that it happened exactly when I did a git-svn
update in the other window. :)
So, maybe I'll just toss this archive. Oh wait, can I back it up a few dozen
revs and try to roll forward? That might be interesting.
git-reset --hard HEAD~10
blow away everything you had me blow away last time
make git-svn equal to HEAD
git-svn rebuild
git-svn fetch
Lemme try that.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
next prev parent reply other threads:[~2006-12-05 4:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 4:00 latest update to git-svn blows up for me Randal L. Schwartz
2006-12-04 7:00 ` Eric Wong
2006-12-04 11:41 ` Randal L. Schwartz
2006-12-04 18:12 ` Eric Wong
2006-12-04 19:36 ` Randal L. Schwartz
2006-12-04 19:54 ` Eric Wong
2006-12-04 20:04 ` Randal L. Schwartz
2006-12-04 20:08 ` Eric Wong
2006-12-04 20:10 ` Randal L. Schwartz
2006-12-04 20:51 ` Eric Wong
2006-12-05 4:08 ` Eric Wong
2006-12-05 4:19 ` Randal L. Schwartz [this message]
2006-12-05 4:33 ` Randal L. Schwartz
2006-12-05 9:13 ` Eric Wong
2006-12-05 16:47 ` Linus Torvalds
2006-12-08 9:55 ` [PATCH] git-svn: extra error check to ensure we open a file correctly Eric Wong
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=86slfvj7oi.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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.