gbmap: Tried to adopt the gbmap name more consistently

Having gbmap/bmap used in different places for the same thing was
confusing. Preferring gbmap as it is consistent with other gstate (grm
queue, gcksums), even if it is a bit noisy.

It's interesting to note what didn't change:

- The BM* range tags: LFS3_TAG_BMFREE, etc. These already differs from
  the GBMAP* prefix enough, and adopting GBM* would risk confusion for
  actual gstate.

- The gbmap revdbg string: "bb~r". We don't have enough characters for
  anything else!

- dbgbmap.py/dbgbmapsvg.py. These aren't actually related to the gbmap,
  so the name difference is a good thing.

This commit is contained in:

Christopher Haster

2025-10-06 14:05:31 -05:00

parent 9d322741ca

commit 9b4ee982bc

14 changed files with 488 additions and 487 deletions

									
										tests/test_grow.toml
									
		+1
		-1
	
												View File
												
				@@ -9,7 +9,7 @@ after = [

				]

				# TODO!! lfs3_fs_grow needs to be able to adjust an on-disk bmaps

				ifndef = 'LFS3_BMAP'

				ifndef = 'LFS3_GBMAP'

				# test we can mount a filesystem with fewer blocks