[gtksourceview: 1/2] doc: correct typo in HACKING
- From: Christian Hergert <chergert src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gtksourceview: 1/2] doc: correct typo in HACKING
- Date: Thu, 30 Jun 2022 17:29:48 +0000 (UTC)
commit 34ba9e99305ec37a3fc3be3264902179771f7fe9
Author: Erik Faye-Lund <kusmabite gmail com>
Date: Thu Jun 30 10:17:32 2022 +0000
doc: correct typo in HACKING
HACKING | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/HACKING b/HACKING
index a3e20fe4..38d68922 100644
--- a/HACKING
+++ b/HACKING
@@ -135,7 +135,7 @@ Here are some general advices:
underlying library.
- Public API should have precondition guards using g_return_if_fail() or
- g_return_val_if_fail(). Optionally, you may do this before returnin values
+ g_return_val_if_fail(). Optionally, you may do this before returning values
from the function to help catch bugs earlier in the development cycle.
Private functions (such as those with static) should use g_assert() to
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]