From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal for a Universal Remote-ID File
Date: Sat, 23 Sep 2023 10:35:00 -0400 [thread overview]
Message-ID: <9903cff52c87709b6a9a47c0bc9e2509ad401ef2.camel@gentoo.org> (raw)
In-Reply-To: <e652e4ee-6e1d-edfa-ef87-fb3e6e1093a8@gmail.com>
On Sat, 2023-09-23 at 00:10 +0530, Siddhanth Rathod wrote:
>
> By establishing a universal remote-ID file, we can streamline this
> process. Your thoughts and feedback on this proposal would be greatly
> appreciated.Also, Any preferences on format?
Building the wiki page isn't too hard, but what's the plan to propagate
changes into those seven other repositories? If we're still
copy/pasting the output of some tool, then we haven't really saved a
step, we've only changed what we're copy/pasting.
next prev parent reply other threads:[~2023-09-23 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 18:40 [gentoo-dev] Proposal for a Universal Remote-ID File Siddhanth Rathod
2023-09-23 7:17 ` Ulrich Mueller
2023-09-23 14:16 ` Sam James
2023-09-23 14:35 ` Michael Orlitzky [this message]
2023-09-23 14:39 ` Sam James
2023-09-23 14:47 ` Michael Orlitzky
2023-09-24 17:44 ` Siddhanth Rathod
2023-09-24 20:15 ` Michael Orlitzky
2023-09-23 15:15 ` Ionen Wolkens
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=9903cff52c87709b6a9a47c0bc9e2509ad401ef2.camel@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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