From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Mark Wielaard <mark@klomp.org>,
Claudio Bantaloukas <claudio.bantaloukas@arm.com>
Subject: Re: Considerations on a gitlab-style forge
Date: Thu, 11 Apr 2024 18:23:24 -0400 [thread overview]
Message-ID: <20240411222324.GA12335@redhat.com> (raw)
In-Reply-To: <7e164cb4-6385-4c2a-b916-3d9631844d87@arm.com>
Hi -
> Thank you for answering, I've been trying to come up with a high level
> reason why something about those forges is desirable to people like me
> and the best I could come up with is this.
>
> Having a single place where a developer can see:
> [...]
> - any code review comments their fellow developers may have
Yeah, that seems to be the main benefit, easier than email threads.
> - whether these changes are likely to break things for others
That's hard to know unless you share code & inter-merge, which is not
automatic in web-forge type systems, and can be done via personal or
development branches in the current system too.
> - what others are working on
(You cannot know that. :-)
> - that doesn't feel like Donald Norman's proverbial teapot!
No comment!
- FChE
next prev parent reply other threads:[~2024-04-11 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 9:35 Claudio Bantaloukas
2024-04-10 13:57 ` Mark Wielaard
2024-04-11 13:17 ` Claudio Bantaloukas
2024-04-11 22:23 ` Frank Ch. Eigler [this message]
2024-04-12 17:37 ` Claudio Bantaloukas
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=20240411222324.GA12335@redhat.com \
--to=fche@redhat.com \
--cc=claudio.bantaloukas@arm.com \
--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).