/brz/remove-bazaar

To get this branch, use:
bzr branch http://gegoxaren.bato24.eu/bzr/brz/remove-bazaar

« back to all changes in this revision

Viewing changes to doc/developers/case-insensitive-file-systems.txt

  • Committer: Jelmer Vernooij
  • Date: 2019-01-02 18:49:15 UTC
  • mto: This revision was merged to the branch mainline in revision 7235.
  • Revision ID: jelmer@jelmer.uk-20190102184915-0da9k4jk49kql994
Fix import for git-objects.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/case-insensitive-file-systems.txt
9
9
For example, the FAT32 file-system is most commonly found on Windows operating
10
10
systems, and has the characteristics usually associated with a Windows
11
11
file-system.  However, USB devices means FAT32 file-systems are often used
12
 
with Linux, so the current operating system doesn't necessarily reflect the
 
12
with GNU/Linux systems, so the current operating system doesn't necessarily reflect the
13
13
capabilities of the file-system.
14
14
 
15
15
Bazaar supports 3 kinds of file-systems, each to different degrees.
16
16
 
17
17
* Case-sensitive file-systems: This is the file-system generally used on
18
 
  Linux - 2 files can differ only by case, and the exact case must be used
 
18
  GNU/Linux: 2 files can differ only by case, and the exact case must be used
19
19
  when opening a file.
20
20
 
21
21
* Case-insensitive, case-preserving (cicp) file-systems: This is the
32
32
relevant to a modern Bazaar.
33
33
 
34
34
For more details, including use cases, please see
35
 
http://bazaar-vcs.org/CasePreservingWorkingTreeUseCases
 
35
http://wiki.bazaar.canonical.com/CasePreservingWorkingTreeUseCases
36
36
 
37
37
Handling these file-systems
38
38
---------------------------
66
66
  accidentally creating 2 inventory items that differ only by case.
67
67
 
68
68
* If an argument results in the creation of a *new* filename (eg, a move
69
 
  destination), the argument will be used as specified.  Bzr will create
 
69
  destination), the argument will be used as specified.  Breezy will create
70
70
  a file and inventory item that exactly matches the case specified (although
71
71
  as above, care must be taken to avoid creating two inventory items that
72
72
  differ only by case.)
84
84
  of the result to match any existing items.
85
85
 
86
86
* Tree.get_canonical_inventory_path - somewhat like Tree.get_symlink_target(),
87
 
  Tree.get_file_by_path() etc; returns a name with the case adjusted to match
 
87
  Tree.get_file() etc; returns a name with the case adjusted to match
88
88
  existing inventory items.
89
89
 
90
90
* osutils.canonical_relpaths() and Tree.get_canonical_inventory_paths() - like