From: Petr Baudis <pasky@ucw.cz>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-mm1
Date: Sun, 24 Sep 2006 15:22:13 +0200 [thread overview]
Message-ID: <20060924132213.GE11916@pasky.or.cz> (raw)
In-Reply-To: <20060924124647.GB25666@flint.arm.linux.org.uk>
Dear diary, on Sun, Sep 24, 2006 at 02:46:47PM CEST, I got a letter
where Russell King <rmk+lkml@arm.linux.org.uk> said that...
> On Sun, Sep 24, 2006 at 04:02:15AM -0700, Andrew Morton wrote:
> > git-arm.patch
>
> It's worth pointing out that something has gone horribly wrong in the
> devel branch of this tree, resulting in a load of files being deleted
> which shouldn't have been.
>
> Absolutely no idea how that happened, but it's a commit buried behind
> lots of other commits and has taken some 4 days to be spotted. At a
> guess, a perl bug where a new associative array somehow manages to pick
> up on old values and forget values from previous assignments.
>
> Oddly, running the script in debug mode (where the only things which
> don't happen is the git commands get called) appears to give correct
> behaviour.
>
> So I'm in the situation where I need to rebuild 4 days work in the ARM
> devel tree. ;(
If I understand correctly, you just need to get rid of that bad commit?
Can you copy the missing files (in the suitable tree structure) to
/tmp/missing/ and try this?
cg-admin-rewritehist -r EVILCOMMIT \
--tree-filter 'cp -r /tmp/missing/* .' \
--commit-filter \
'if [ "$GIT_COMMIT" = "EVILCOMMIT" ]; then
shift;
while [ -n "$1" ]; do
shift; echo "$1"; shift;
done;
else
git-commit-tree "$@";
fi' \
fixedbranch
(s/EVILCOMMIT/thesha1id/)
Now check if fixedbranch looks ok.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
next prev parent reply other threads:[~2006-09-24 13:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 11:02 2.6.18-mm1 Andrew Morton
2006-09-24 12:46 ` 2.6.18-mm1 Russell King
2006-09-24 13:11 ` 2.6.18-mm1 Russell King
2006-09-24 13:22 ` Petr Baudis [this message]
2006-09-24 14:20 ` 2.6.18-mm1 Russell King
2006-09-24 14:29 ` 2.6.18-mm1 Petr Baudis
2006-09-24 14:47 ` 2.6.18-mm1 Russell King
2006-09-24 16:55 ` 2.6.18-mm1 Petr Baudis
2006-09-24 18:48 ` 2.6.18-mm1 Junio C Hamano
2006-09-24 21:34 ` 2.6.18-mm1 Russell King
2006-09-24 21:56 ` 2.6.18-mm1 Andrew Morton
2006-09-24 22:07 ` 2.6.18-mm1 Junio C Hamano
2006-09-24 16:35 ` 2.6.18-mm1 Dmitry Torokhov
2006-09-24 17:06 ` 2.6.18-mm1 Andrew Morton
2006-09-27 2:04 ` 2.6.18-mm1 Eric W. Biederman
2006-09-27 3:11 ` 2.6.18-mm1 Andrew Morton
2006-09-27 5:12 ` 2.6.18-mm1 Eric W. Biederman
2006-09-27 5:44 ` 2.6.18-mm1 Aaron Durbin
2006-09-27 6:20 ` 2.6.18-mm1 Eric W. Biederman
2006-09-27 7:13 ` 2.6.18-mm1 Andi Kleen
2006-09-27 7:39 ` 2.6.18-mm1 Eric W. Biederman
2006-09-27 7:51 ` 2.6.18-mm1 Andi Kleen
2006-09-27 14:08 ` 2.6.18-mm1 Eric W. Biederman
2006-09-27 22:06 ` 2.6.18-mm1 Aaron Durbin
2006-09-27 23:06 ` 2.6.18-mm1 Andrew Morton
2006-09-27 9:25 ` 2.6.18-mm1 Andy Whitcroft
2006-09-27 16:12 ` 2.6.18-mm1 Andrew Morton
2006-09-27 16:50 ` 2.6.18-mm1 Andy Whitcroft
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=20060924132213.GE11916@pasky.or.cz \
--to=pasky@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®