From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org, overseers@sourceware.org,
elfutils-devel@lists.fedorahosted.org
Subject: Re: sourceware hosting for elfutils
Date: Thu, 22 Dec 2016 14:05:00 -0000 [thread overview]
Message-ID: <20161222140524.GB4817@redhat.com> (raw)
In-Reply-To: <1482412423.14558.146.camel@klomp.org>
Hi, Mark -
> > > - A mailinglist elfutils-devel that is open for posting by anybody
>
> I don't see it listed at https://sourceware.org/lists.html [...]
Is now.
> If I give you the current subscriber list of fedorahosted elfutils-devel
> could we mass subscribe everybody to the new list? There are about 100
> people on the list.
Yes.
> > Sort of done, but had to be undone because the old fedora mbox
> > archives were not spam-filtered. [...]
>
> Sorry about that. I can try to create a spam free mbox by running
> everything through spamassassin first and removing everything marked if
> that is helpful.
Sure.
> > [...]
> > Done, ftp://sourceware.org/pub/elfutils and http://sourceware.org/elfutils/ftp/> > point to a directory you can use, with those old archives all imported.
>
> Awesome. What is the official way to upload new releases there?
Log onto sourceware and deposit files under /sourceware/ftp/pub/elfutils/ .
> [...]
> Thanks. I see elfutils as product now in https://sourceware.org/bugzilla
> Could we get as components libelf, libdw, libasm, backends, tools and
> general/unknown?
Done.
> > > that get emails for git commits, bug creation/modifications [etc.]
> [...]
OK, will look into this soon.
- FChE
prev parent reply other threads:[~2016-12-22 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1481538832.14558.82.camel@klomp.org>
2016-12-22 0:50 ` Frank Ch. Eigler
2016-12-22 13:14 ` Mark Wielaard
2016-12-22 14:05 ` Frank Ch. Eigler [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=20161222140524.GB4817@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@lists.fedorahosted.org \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.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).