From: Julian Seward <jseward@acm.org>
To: Mark Wielaard <mark@klomp.org>, bzip2-devel@sourceware.org
Subject: Re: [PATCH] Replace project contact email with bzip2-devel@sourceware.org.
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <06d57235-b5c4-fd7c-6471-656735420e8c@acm.org> (raw)
In-Reply-To: <1562868211-28019-1-git-send-email-mark@klomp.org>
Hi Mark,
That's all absolutely fine. Please do update as per your patch.
J
On 11/07/2019 20:03, Mark Wielaard wrote:
> Hi Julian,
>
> As discussed on irc this updates the contact information to the
> community mailinglist instead of it all going to you personally.
> I'll update the website and generated manual too. I'll also remove
> this paragraph from the website:
>
> If you can be bothered, please
> <a href="mailto:jseward@acm.org">email me</a> to say you've got a
> copy. It's nice to know where this stuff gets to.
>
> Unless you want to keep that.
>
> Cheers,
>
> Mark
>
> Keep Julian's email as author information, but redirect general
> project feedback in the code and manual to the community mailinglist.
> ---
> README | 4 ++--
> bzip2.c | 8 ++++----
> bzlib.c | 4 ++--
> entities.xml | 3 ++-
> manual.xml | 8 ++++----
> 5 files changed, 14 insertions(+), 13 deletions(-)
>
> diff --git a/README b/README
> index 64873f9..42543d1 100644
> --- a/README
> +++ b/README
> @@ -165,8 +165,8 @@ WHAT'S NEW IN 1.0.x ?
>
> See the CHANGES file.
>
> -I hope you find bzip2 useful. Feel free to contact me at
> - jseward@acm.org
> +I hope you find bzip2 useful. Feel free to contact the developers at
> + bzip2-devel@sourceware.org
> if you have any suggestions or queries. Many people mailed me with
> comments, suggestions and patches after the releases of bzip-0.15,
> bzip-0.21, and bzip2 versions 0.1pl2, 0.9.0, 0.9.5, 1.0.0, 1.0.1,
> diff --git a/bzip2.c b/bzip2.c
> index 76c6c94..01a41d2 100644
> --- a/bzip2.c
> +++ b/bzip2.c
> @@ -748,8 +748,8 @@ void panic ( const Char* s )
> fprintf ( stderr,
> "\n%s: PANIC -- internal consistency error:\n"
> "\t%s\n"
> - "\tThis is a BUG. Please report it to me at:\n"
> - "\tjseward@acm.org\n",
> + "\tThis is a BUG. Please report it to:\n"
> + "\tbzip2-devel@sourceware.org\n",
> progName, s );
> showFileNames();
> cleanUpAndFail( 3 );
> @@ -829,7 +829,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n )
> " The user's manual, Section 4.3, has more info on (1) and (2).\n"
> " \n"
> " If you suspect this is a bug in bzip2, or are unsure about (1)\n"
> - " or (2), feel free to report it to me at: jseward@acm.org.\n"
> + " or (2), feel free to report it to: bzip2-devel@sourceware.org.\n"
> " Section 4.3 of the user's manual describes the info a useful\n"
> " bug report should have. If the manual is available on your\n"
> " system, please try and read it before mailing me. If you don't\n"
> @@ -852,7 +852,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n )
> " The user's manual, Section 4.3, has more info on (2) and (3).\n"
> " \n"
> " If you suspect this is a bug in bzip2, or are unsure about (2)\n"
> - " or (3), feel free to report it to me at: jseward@acm.org.\n"
> + " or (3), feel free to report it to: bzip2-devel@sourceware.org.\n"
> " Section 4.3 of the user's manual describes the info a useful\n"
> " bug report should have. If the manual is available on your\n"
> " system, please try and read it before mailing me. If you don't\n"
> diff --git a/bzlib.c b/bzlib.c
> index f9da295..2dbe666 100644
> --- a/bzlib.c
> +++ b/bzlib.c
> @@ -43,12 +43,12 @@ void BZ2_bz__AssertH__fail ( int errcode )
> fprintf(stderr,
> "\n\nbzip2/libbzip2: internal error number %d.\n"
> "This is a bug in bzip2/libbzip2, %s.\n"
> - "Please report it to me at: jseward@acm.org. If this happened\n"
> + "Please report it to: bzip2-devel@sourceware.org. If this happened\n"
> "when you were using some program which uses libbzip2 as a\n"
> "component, you should also report this bug to the author(s)\n"
> "of that program. Please make an effort to report this bug;\n"
> "timely and accurate bug reports eventually lead to higher\n"
> - "quality software. Thanks. Julian Seward, 10 December 2007.\n\n",
> + "quality software. Thanks.\n\n",
> errcode,
> BZ2_bzlibVersion()
> );
> diff --git a/entities.xml b/entities.xml
> index 3016674..a415062 100644
> --- a/entities.xml
> +++ b/entities.xml
> @@ -1,6 +1,7 @@
> <!-- misc. strings -->
> <!ENTITY bz-url "https://sourceware.org/bzip2/">
> -<!ENTITY bz-email "jseward@acm.org">
> +<!ENTITY bz-author "jseward@acm.org">
> +<!ENTITY bz-email "bzip2-devel@sourceware.org">
> <!ENTITY bz-lifespan "1996-2010">
>
> <!ENTITY bz-version "1.0.7">
> diff --git a/manual.xml b/manual.xml
> index b177bbf..b99e480 100644
> --- a/manual.xml
> +++ b/manual.xml
> @@ -653,7 +653,7 @@ unsigned 64-bit integer.</para>
> <title>AUTHOR</title>
>
> <para>Julian Seward,
> -<computeroutput>&bz-email;</computeroutput></para>
> +<computeroutput>&bz-author;</computeroutput></para>
>
> <para>The ideas embodied in
> <computeroutput>bzip2</computeroutput> are due to (at least) the
> @@ -2487,12 +2487,12 @@ message:</para>
> <blockquote>
> <para>bzip2/libbzip2: internal error number N.</para>
> <para>This is a bug in bzip2/libbzip2, &bz-version; of &bz-date;.
> -Please report it to me at: &bz-email;. If this happened
> +Please report it to: &bz-email;. If this happened
> when you were using some program which uses libbzip2 as a
> component, you should also report this bug to the author(s)
> of that program. Please make an effort to report this bug;
> timely and accurate bug reports eventually lead to higher
> -quality software. Thanks. Julian Seward, &bz-date;.
> +quality software. Thanks.
> </para></blockquote>
>
> <para>where <computeroutput>N</computeroutput> is some error code
> @@ -2537,7 +2537,7 @@ recovered from.</para>
> <para>Everything related to Windows has been contributed by
> Yoshioka Tsuneo
> (<computeroutput>tsuneo@rr.iij4u.or.jp</computeroutput>), so
> -you should send your queries to him (but perhaps Cc: me,
> +you should send your queries to him (but please Cc:
> <computeroutput>&bz-email;</computeroutput>).</para>
>
> <para>My vague understanding of what to do is: using Visual C++
>
next prev parent reply other threads:[~2019-07-12 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Mark Wielaard
2019-01-01 0:00 ` Julian Seward [this message]
2019-01-01 0:00 ` 1.0.8 release (Was: [PATCH] Replace project contact email with bzip2-devel@sourceware.org) Mark Wielaard
2019-01-01 0:00 ` [PATCH] Replace project contact email with bzip2-devel@sourceware.org Mark Wielaard
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=06d57235-b5c4-fd7c-6471-656735420e8c@acm.org \
--to=jseward@acm.org \
--cc=bzip2-devel@sourceware.org \
--cc=mark@klomp.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 read-only IMAP folder(s) and NNTP newsgroup(s).