From: pi3orama <pi3orama@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: ReBranch - a record-replay debugging tool
Date: Thu, 09 Jun 2011 12:54:00 -0000 [thread overview]
Message-ID: <4DF0C229.1030407@gmail.com> (raw)
In-Reply-To: <201106091325.59412.pedro@codesourcery.com>
I have add GDB's copyright notice back, you can check for it in the git
repository: https://gitorious.org/rebranch
A comparison of GDB record/replay and ReBranch has been added to the
google code site.
A pdf describe the mechanism of ReBranch has been uploaded to the site
and google doc:
http://rebranch.googlecode.com/hg/wiki/rebranch.pdf
https://docs.google.com/viewer?a=v&pid=explorer&chrome=true&srcid=0B1hummTQgSY1NTVhY2FkM2MtZDkxZi00ZDVhLTljNTQtMTZhMjZiMDI3ODZi&hl=en_US
Thank you for your kindly advise.
> On Thursday 09 June 2011 12:57:18, pi3orama@gmail.com wrote:
>> Thank you for your advise. I have changed license, added a COPYING file in
>> the code, and added copyright header into every source files.
> Thanks a bunch!
>
> One detail. Files that had been derived from other GPL files
> should not lose the original copyright notice. Of course
> you can _add_ a note on your own copyright. That is, e.g.,
> on exception.h|c, I suggest something like:
>
> /* Copyright (C) 1986, 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996,
> 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008,
> 2009, 2010, 2011 Free Software Foundation, Inc.
>
> Copyright (C) 2009, 2010, 2011 Nan Wang
>
> This file is part of ReBranch. Originally based on exceptions.c from GDB.
> */
>
> (there may be other files, I really haven't checked)
>
>
> Still very much looking forward for a high level outline of ReBranch's
> record/replay strategy, and how it differs from GDB's target record. :-)
>
next prev parent reply other threads:[~2011-06-09 12:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bcaec5395f2aa367da04a5462782@google.com>
2011-06-09 12:26 ` Pedro Alves
2011-06-09 12:54 ` pi3orama [this message]
2011-06-09 14:37 ` Joel Brobecker
2011-06-09 14:51 ` Pedro Alves
[not found] ` <BANLkTi=Mk0-PXb=7m0RZvEt7jegz17JXHw@mail.gmail.com>
2011-06-09 16:11 ` pi3orama
2011-06-09 16:20 ` Pedro Alves
2011-06-13 1:57 Robert Bu
2011-06-13 2:03 ` pi3orama
-- strict thread matches above, loose matches on Subject: below --
2011-06-09 16:39 Nan Wang
2011-06-09 19:20 ` paawan oza
[not found] ` <bcaec5215b03b867ea04a5500b35@google.com>
2011-06-10 1:55 ` pi3orama
2011-06-10 8:04 ` paawan oza
2011-06-10 8:15 ` pi3orama
2011-06-10 9:14 ` paawan oza
2011-06-10 9:36 ` pi3orama
2011-06-10 5:51 ` Yao Qi
2011-06-10 6:39 ` pi3orama
[not found] <1307602807.17016.ezmlm@sourceware.org>
2011-06-09 7:23 ` pi3orama
2011-06-09 9:27 ` Pedro Alves
2011-06-09 10:32 ` paawan oza
2011-06-09 13:05 ` pi3orama
[not found] ` <4DF0A729.4070106@gmail.com>
2011-06-09 11:23 ` Pedro Alves
2011-06-09 12:06 ` pi3orama
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=4DF0C229.1030407@gmail.com \
--to=pi3orama@gmail.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
/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