From: Petr Baudis <pasky@suse.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-mm1
Date: Sun, 24 Sep 2006 16:29:58 +0200 [thread overview]
Message-ID: <20060924142958.GU13132@pasky.or.cz> (raw)
In-Reply-To: <20060924142005.GF25666@flint.arm.linux.org.uk>
Dear diary, on Sun, Sep 24, 2006 at 04:20:06PM CEST, I got a letter
where Russell King <rmk+lkml@arm.linux.org.uk> said that...
> I'm now told that the resulting tree after all the commits is correct.
> The problem is that all the files which were supposed to be deleted by
> previous patches ended up actually being deleted by the final patch in
> the series.
>
> So the resulting tree is fine, it's just that the history is rather
> broken.
Well, that rewritehist batch should work fine even in this case.
(Of course that's assuming that no change was supposed to happen to
those files in the last four days.)
> I think a solution to this might be to use git-apply, but there's one
> draw back - I currently have the facility to unpatch at a later date,
> but git-apply doesn't support -R.
Yes, if there's not too many patches perhaps using git-apply -R would be
simpler. git-apply in git-1.4.2.1 does support -R.
--
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 14:30 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 ` 2.6.18-mm1 Petr Baudis
2006-09-24 14:20 ` 2.6.18-mm1 Russell King
2006-09-24 14:29 ` Petr Baudis [this message]
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=20060924142958.GU13132@pasky.or.cz \
--to=pasky@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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®