public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: frysk@sourceware.org
Cc: timoore@redhat.com
Subject: This diff a bit weird Re: [SCM] frysk system monitor/debugger branch,  master, updated. 6c1b2134a1081b7d65f0656fcc13a9ae85d964f9
Date: Tue, 06 Nov 2007 15:13:00 -0000	[thread overview]
Message-ID: <473084A9.60700@redhat.com> (raw)
In-Reply-To: <20071106145806.11940.qmail@sourceware.org>

pmuldoon@sourceware.org wrote:

Not sure what is going on here but:

> The branch, master has been updated
>       via  6c1b2134a1081b7d65f0656fcc13a9ae85d964f9 (commit)
>       from  7c185652b3cca2ab1cbfeeb45482ec772d1b4c5b (commit)
>
>   

The diff below is diffing a new file (CorefileStatus.java) with an 
existing file (DeadHost.java):

> diff --git a/frysk-core/frysk/proc/dead/DeadHost.java b/frysk-core/frysk/proc/dead/CorefileStatus.java
> similarity index 88%
> copy from frysk-core/frysk/proc/dead/DeadHost.java
> copy to frysk-core/frysk/proc/dead/CorefileStatus.java
> index 29a077e..b99e1fc 100644
> --- a/frysk-core/frysk/proc/dead/DeadHost.java
> +++ b/frysk-core/frysk/proc/dead/CorefileStatus.java
> @@ -33,20 +33,18 @@
>  // this exception. If you modify this file, you may extend this
>  // exception to your version of the file, but you are not obligated to
>  // do so. If you do not wish to provide this exception without
> -// modification, you must delete this exception statement from your
> -// version and license this file solely under the GPL without
> +// modification, you must delete this exception statement from your// version and license this file solely under the GPL without
>  // exception.
>   


And so on. Maybe it was my commit, too?

Regards

Phil

           reply	other threads:[~2007-11-06 15:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20071106145806.11940.qmail@sourceware.org>]

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=473084A9.60700@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=timoore@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).