public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: v <vsochat@gmail.com>
To: Dodji Seketeli <dodji@seketeli.org>
Cc: v via Libabigail <libabigail@sourceware.org>,
	Mark Wielaard <mark@klomp.org>, Ben Woodard <woodard@redhat.com>
Subject: Re: Thinking different (was Re: Testing Setup - More Tests and Automation?)
Date: Thu, 9 Jun 2022 13:48:47 -0600	[thread overview]
Message-ID: <CAM=pu+JOGsmj1FUytzWBZvswH7W3jM1fs715aV=0BZ+BtXEu-Q@mail.gmail.com> (raw)
In-Reply-To: <87a6amkr83.fsf_-_@seketeli.org>

I think we could have a GitHub org for libabigail
https://github.com/libabigail that updated itself nightly with the
sourceware remote, and then take pull requests there that are transformed
into patches and submit by some means. If Ben can walk me through what
happens behind the scenes when he does that I can probably make specific
suggestions. If there is a programmatic way to submit to the list we can
probably get GitHub content there too (the other direction). We can do
everything from posting issues to pull requests (to really whatever content
you want from the list - the GitHub APIs are amazing).

If we pull from sourceware I don't think you'd require an account Dodji,
but if you wanted to try out GitHub and have fun on there with respect to
discussions, issues, I highly recommend it :) Maybe your username would be
https://github.com/masterdodji?

Ben - ping me when you are around and we can talk about these logistics!
Maybe we could write up a concrete plan and present it to Dodji et. al.

Best,

V

On Thu, Jun 9, 2022 at 5:31 AM Dodji Seketeli <dodji@seketeli.org> wrote:

> Hello,
>
> In concrete terms, would it be possible to, say, be able to interact
> with those who want it via email (for instance, be able to just post
> patches to this mailing list) AND ALSO via (git{hub,lab}) pull requests
> (whose notifications would be sent to this list)?
>
> In that case I understand that I would have, indeed, to have an account
> on all those platforms, to pull the code.  But maybe I wouldn't be
> forcing all of you to do so.
>
> Would that be feasible? How? Or is there a better way forward?
>
> I am really trying to move the needle forward here.
>
> Thanks.
>
> --
>                 Dodji
>

  reply	other threads:[~2022-06-09 19:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAM=pu++-JdBdizXQ9dj8eUypXg7fpPOTDzN6BL1NY-TFvk++kQ@mail.gmail.com>
2022-04-28  0:55 ` Fwd: Testing Setup - More Tests and Automation? Ben Woodard
2022-04-28  1:57   ` v
2022-04-30 19:55     ` Mark Wielaard
2022-04-30 20:36       ` v
2022-04-30 21:48         ` Mark Wielaard
2022-04-30 22:38           ` v
2022-05-01 22:42             ` Mark Wielaard
2022-05-01 22:46               ` v
2022-06-09 11:31             ` Thinking different (was Re: Testing Setup - More Tests and Automation?) Dodji Seketeli
2022-06-09 19:48               ` v [this message]
2022-06-15 14:21                 ` Dodji Seketeli
2022-06-09 11:18         ` Testing Setup - More Tests and Automation? Dodji Seketeli
2022-06-09 11:11       ` Dodji Seketeli
2022-06-14 10:05         ` Mark Wielaard
2022-04-28  8:06   ` Fwd: " Mark Wielaard
2022-04-29 21:13     ` Mark Wielaard
2022-04-29 22:02       ` Mark Wielaard
2022-05-03 19:08       ` Ben Woodard

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='CAM=pu+JOGsmj1FUytzWBZvswH7W3jM1fs715aV=0BZ+BtXEu-Q@mail.gmail.com' \
    --to=vsochat@gmail.com \
    --cc=dodji@seketeli.org \
    --cc=libabigail@sourceware.org \
    --cc=mark@klomp.org \
    --cc=woodard@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).