From ea86742059a7eebee9dd38810a2146bd8235d544 Mon Sep 17 00:00:00 2001
From: Shnatsel <Shnatsel@users.noreply.github.com>
Date: Mon, 18 Jan 2021 21:10:35 +0000
Subject: [PATCH] Assigned RUSTSEC-2020-0097 to xcb

---
 crates/xcb/{RUSTSEC-0000-0000.md => RUSTSEC-2020-0097.md} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename crates/xcb/{RUSTSEC-0000-0000.md => RUSTSEC-2020-0097.md} (95%)

diff --git a/crates/xcb/RUSTSEC-0000-0000.md b/crates/xcb/RUSTSEC-2020-0097.md
similarity index 95%
rename from crates/xcb/RUSTSEC-0000-0000.md
rename to crates/xcb/RUSTSEC-2020-0097.md
index a894a44..0d534d1 100644
--- a/crates/xcb/RUSTSEC-0000-0000.md
+++ b/crates/xcb/RUSTSEC-2020-0097.md
@@ -1,6 +1,6 @@
 ```toml
 [advisory]
-id = "RUSTSEC-0000-0000"
+id = "RUSTSEC-2020-0097"
 package = "xcb"
 date = "2020-12-10"
 url = "https://github.com/rtbo/rust-xcb/issues/93"
@@ -17,4 +17,4 @@ patched = []
 With this definition, it is possible to create a `base::Error` with an invalid pointer and trigger memory safety errors
 such as use-after-free or double-free with safe Rust.
 
-The users of `xcb` crate are advised not to manipulate the field.
\ No newline at end of file
+The users of `xcb` crate are advised not to manipulate the field.