* [PATCH] Add config file so b4 uses inbox.sourceware.org automatically
@ 2024-05-23 15:49 Jonathan Wakely
2024-06-03 20:33 ` Jeff Law
2024-07-28 10:13 ` [committed v2] " Jonathan Wakely
0 siblings, 2 replies; 3+ messages in thread
From: Jonathan Wakely @ 2024-05-23 15:49 UTC (permalink / raw)
To: gcc-patches
It looks like my patch[1] to make b4 figure this out automagically won't
be accepted, so this makes it work for GCC. A similar commit could be
done for each project hosted on sourceware.org if desired.
[1] https://lore.kernel.org/tools/20240523143752.385810-1-jwakely@redhat.com/T/#u
OK for trunk?
-- >8 --
This makes b4 use inbox.sourceware.org instead of the default host
lore.kernel.org, so that every b4 user doesn't have to configure this
themselves.
ChangeLog:
* .b4-config: New file.
---
.b4-config | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 .b4-config
diff --git a/.b4-config b/.b4-config
new file mode 100644
index 00000000000..d5ba8e08446
--- /dev/null
+++ b/.b4-config
@@ -0,0 +1,3 @@
+[b4]
+ midmask = https://inbox.sourceware.org/%s
+ linkmask = https://inbox.sourceware.org/%s
--
2.45.1
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] Add config file so b4 uses inbox.sourceware.org automatically
2024-05-23 15:49 [PATCH] Add config file so b4 uses inbox.sourceware.org automatically Jonathan Wakely
@ 2024-06-03 20:33 ` Jeff Law
2024-07-28 10:13 ` [committed v2] " Jonathan Wakely
1 sibling, 0 replies; 3+ messages in thread
From: Jeff Law @ 2024-06-03 20:33 UTC (permalink / raw)
To: Jonathan Wakely, gcc-patches
On 5/23/24 9:49 AM, Jonathan Wakely wrote:
> It looks like my patch[1] to make b4 figure this out automagically won't
> be accepted, so this makes it work for GCC. A similar commit could be
> done for each project hosted on sourceware.org if desired.
>
> [1] https://lore.kernel.org/tools/20240523143752.385810-1-jwakely@redhat.com/T/#u
>
> OK for trunk?
>
> -- >8 --
>
> This makes b4 use inbox.sourceware.org instead of the default host
> lore.kernel.org, so that every b4 user doesn't have to configure this
> themselves.
>
> ChangeLog:
>
> * .b4-config: New file.
Given the impact on anyone not using b4 is nil and it makes life easier
for those using b4, this seems trivially OK for the trunk.
jeff
^ permalink raw reply [flat|nested] 3+ messages in thread
* [committed v2] Add config file so b4 uses inbox.sourceware.org automatically
2024-05-23 15:49 [PATCH] Add config file so b4 uses inbox.sourceware.org automatically Jonathan Wakely
2024-06-03 20:33 ` Jeff Law
@ 2024-07-28 10:13 ` Jonathan Wakely
1 sibling, 0 replies; 3+ messages in thread
From: Jonathan Wakely @ 2024-07-28 10:13 UTC (permalink / raw)
To: libstdc++, gcc-patches
Jeff approved an earlier version of this as trivially OK (since it
doesn't affect anybody not using b4). The v2 patch that I've pushed adds
the send-series-to config, as suggested by the b4 maintainer here:
https://lore.kernel.org/tools/20240523143752.385810-1-jwakely@redhat.com/T/#mb21ebe04b433442f40548acc4394554e65a8d1be
Pushed to trunk.
-- >8 --
This makes b4 use inbox.sourceware.org instead of the default host
lore.kernel.org, so that every b4 user doesn't have to configure this
themselves.
ChangeLog:
* .b4-config: New file.
---
.b4-config | 4 ++++
1 file changed, 4 insertions(+)
create mode 100644 .b4-config
diff --git a/.b4-config b/.b4-config
new file mode 100644
index 00000000000..eec2261deb6
--- /dev/null
+++ b/.b4-config
@@ -0,0 +1,4 @@
+[b4]
+ midmask = https://inbox.sourceware.org/%s
+ linkmask = https://inbox.sourceware.org/%s
+ send-series-to = gcc-patches@gcc.gnu.org
--
2.45.2
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-07-28 10:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-23 15:49 [PATCH] Add config file so b4 uses inbox.sourceware.org automatically Jonathan Wakely
2024-06-03 20:33 ` Jeff Law
2024-07-28 10:13 ` [committed v2] " Jonathan Wakely
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).