From 78c3d1bf03ee09a66f23d622066efbfbcfdeed6a Mon Sep 17 00:00:00 2001
From: Michael Wolf <michael.wolf@elastic.co>
Date: Tue, 15 Oct 2024 13:11:05 -0700
Subject: [PATCH] Update and rename 0000-fileorigin-fields.md to
 0048-fileorigin-fields.md

---
 .../{0000-fileorigin-fields.md => 0048-fileorigin-fields.md}  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename rfcs/text/{0000-fileorigin-fields.md => 0048-fileorigin-fields.md} (98%)

diff --git a/rfcs/text/0000-fileorigin-fields.md b/rfcs/text/0048-fileorigin-fields.md
similarity index 98%
rename from rfcs/text/0000-fileorigin-fields.md
rename to rfcs/text/0048-fileorigin-fields.md
index 6af8416a7..85622991b 100644
--- a/rfcs/text/0000-fileorigin-fields.md
+++ b/rfcs/text/0048-fileorigin-fields.md
@@ -1,8 +1,8 @@
-# 0000: File Origin Fields
+# 0048: File Origin Fields
 <!-- Leave this ID at 0000. The ECS team will assign a unique, contiguous RFC number upon merging the initial stage of this RFC. -->
 
 - Stage: **0 (strawperson)** <!-- Update to reflect target stage. See https://elastic.github.io/ecs/stages.html -->
-- Date: **TBD** <!-- The ECS team sets this date at merge time. This is the date of the latest stage advancement. -->
+- Date: **2024-10-15** <!-- The ECS team sets this date at merge time. This is the date of the latest stage advancement. -->
 
 <!--
 As you work on your RFC, use the "Stage N" comments to guide you in what you should focus on, for the stage you're targeting.