qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Git/SVN/CVS? was Re: [Qemu-devel] What does code_copy_enabled do?
Date: Sat, 9 Feb 2008 08:48:45 +0200	[thread overview]
Message-ID: <f43fc5580802082248p4c339766yc9099482b0ec799a@mail.gmail.com> (raw)

On 2/8/08, Rob Landley <rob@landley.net> wrote:
> On Thursday 07 February 2008 21:52:33 Paul Brook wrote:
> > On Friday 08 February 2008, Rob Landley wrote:
> > > Grepping through the source code, I can find 3 places where this global
> > > variable is set (it's initialized to a default value of 1, there's
> > > a "no-code-copy" command line option that sets it to zero, and then it
> > > shows up in the test suite once).  What I can't find is any code ever
> > > actually checking or using the value put into this variable....
> >
> > It got ripped out a while back.
>
> Any news on the possible cvs->svn migration?  I'd submit a cleanup patch to
> rip out the remaining traces of code_copy_enabled, but the git mirror I
> follow (git://git.kernel.dk/data/git/qemu.git) hasn't updated in several days
> so I'm not actually sure it's still there in cvs.
>
> Just checked and http://savannah.nongnu.org/svn/?group=qemu isn't there
> either...

How about git? I'd like to use git bisect. Would there be problems if
it were possible to commit via more than one interface?

             reply	other threads:[~2008-02-09  6:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09  6:48 Blue Swirl [this message]
2008-02-09 12:45 ` Git/SVN/CVS? was Re: [Qemu-devel] What does code_copy_enabled do? Johannes Schindelin
2008-02-09 14:10   ` Blue Swirl
2008-02-09 14:22     ` Johannes Schindelin
2008-02-09 15:20   ` Felipe Contreras
2008-02-09 16:49     ` Johannes Schindelin
2008-02-08  2:42       ` Rob Landley
2008-02-08  3:52         ` Paul Brook
2008-02-08 20:51           ` Rob Landley
2008-02-11 15:50             ` Ian Jackson
2008-02-11 16:10               ` Johannes Schindelin
2008-02-11 16:12                 ` Ian Jackson
2008-02-11 15:52             ` Ian Jackson
2008-02-11 19:30               ` Felipe Contreras
2008-02-11 20:38                 ` Johannes Schindelin
2008-02-11 21:19                   ` Rob Landley
2008-02-11 21:19                   ` Felipe Contreras
2008-02-12  2:32               ` Paul Brook
2008-02-12  3:46                 ` M. Warner Losh
2008-02-12 11:30                   ` Julian Seward
2008-02-12 11:15                 ` Johannes Schindelin
2008-02-12 12:06                   ` Andreas Färber
2008-02-12 11:57         ` Ian Jackson
2008-02-12 12:51           ` Johannes Schindelin
2008-02-12 12:59             ` Ian Jackson
2008-02-12 13:37               ` Johannes Schindelin
2008-02-12 13:52                 ` Ian Jackson
2008-02-13  8:22           ` Rob Landley
2008-02-13  9:18             ` Felipe Contreras
2008-02-11 21:00       ` Git/SVN/CVS? was " Rob Landley
2008-02-11 21:28         ` Johannes Schindelin
2008-02-12  2:34           ` Rob Landley

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=f43fc5580802082248p4c339766yc9099482b0ec799a@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=paul@codesourcery.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).