From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: qemu-devel@nongnu.org
Subject: Re: [OT] Re: [Qemu-devel] [PATCH] Remove broken MIPS PICA 61 machine
Date: Wed, 30 Jan 2008 13:47:17 +0000 [thread overview]
Message-ID: <20080130134717.GB4340@implementation.uk.xensource.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801301435120.14671@localhost>
Marius Groeger, le Wed 30 Jan 2008 14:41:17 +0100, a écrit :
> On Wed, 30 Jan 2008, Hervé Poussineau wrote:
>
> > I didn't know how to do a patch which removes the file
> > hw/mips_pica61.c, so this file will have to be removed manually by
> > the committer.
>
> One work-around for that is to do:
>
> $ cvs diff ... > my.diff
> $ diff -pu hw/mips_pica61.c /dev/null >> my.diff
Another way is to use cvsdo:
cvsdo rm hw/mips_pica61.c
and then cvs diff will dump the removal.
Samuel
prev parent reply other threads:[~2008-01-30 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 11:32 [Qemu-devel] [PATCH] Remove broken MIPS PICA 61 machine Hervé Poussineau
2008-01-30 13:41 ` [OT] " Marius Groeger
2008-01-30 13:47 ` Samuel Thibault [this message]
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=20080130134717.GB4340@implementation.uk.xensource.com \
--to=samuel.thibault@eu.citrix.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).