All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Katz <katzj@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] email address fix
Date: Wed, 25 May 2005 11:57:50 -0400	[thread overview]
Message-ID: <1117036670.9191.10.camel@bree.local.net> (raw)
In-Reply-To: <E1Daqwq-0005b6-00@mta1.cl.cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 412 bytes --]

On Wed, 2005-05-25 at 09:09 +0100, Keir Fraser wrote:
> I'll leave it to Jeremy to decide whether he wants to obfuscate his
> email address or not.

I think the obfuscation happened due to a patch being pulled from a
mailing list archive at some point or something along those lines.  I
know I didn't ever intentionally do so.

With current unstable, there's only one case left.  Here's the patch for
it

Jeremy

[-- Attachment #2: xen-email.patch --]
[-- Type: text/x-patch, Size: 422 bytes --]

===== tools/pygrub/src/fsys/__init__.py 1.2 vs edited =====
--- 1.2/tools/pygrub/src/fsys/__init__.py	2005-04-27 02:20:37 -04:00
+++ edited/tools/pygrub/src/fsys/__init__.py	2005-05-25 11:56:12 -04:00
@@ -1,6 +1,6 @@
 #
 # Copyright 2005 Red Hat, Inc.
-# Jeremy Katz <katzj@xxxxxxxxxx>
+# Jeremy Katz <katzj@redhat.com>
 #
 # This software may be freely redistributed under the terms of the GNU
 # general public license.

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

      parent reply	other threads:[~2005-05-25 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19 15:42 [PATCH] email address fix aq
2005-05-25  5:57 ` aq
2005-05-25  8:09   ` Keir Fraser
2005-05-25  9:02     ` aq
2005-05-25 15:57     ` Jeremy Katz [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=1117036670.9191.10.camel@bree.local.net \
    --to=katzj@redhat.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.