Skip to content

Fix: update description for mtime in documentation #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix: update description for mtime in documentation #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions write-yourself-a-git.org
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2258,7 +2258,7 @@ mechanism, in the form of what it calls the *index file*.
After a commit, the index file is a sort of copy of that commit: it
holds the same path/blob association than the corresponding tree. But
it also holds extra information about files in the worktree, like
their creation/modification time, so =git status= doesn't often need
their metadata modification/modification time, so =git status= doesn't often need
to actually compare files: it just checks that their modification time
is the same as the one stored in the index file, and only if it isn't
does it perform an actual comparison.
Expand Down Expand Up @@ -2428,10 +2428,10 @@ produce more elegant code in C than in Python…)
content = raw[12:]
idx = 0
for i in range(0, count):
# Read creation time, as a unix timestamp (seconds since
# Read metadata modification time, as a unix timestamp (seconds since
# 1970-01-01 00:00:00, the "epoch")
ctime_s = int.from_bytes(content[idx: idx+4], "big")
# Read creation time, as nanoseconds after that timestamps,
# Read metadata modification time, as nanoseconds after that timestamps,
# for extra precision.
ctime_ns = int.from_bytes(content[idx+4: idx+8], "big")
# Same for modification time: first seconds from epoch.
Expand Down Expand Up @@ -2544,7 +2544,7 @@ so we can display every single bit of info in the index file.
0b1110: "git link" }[e.mode_type]
print(f" {entry_type} with perms: {e.mode_perms:o}")
print(f" on blob: {e.sha}")
print(f" created: {datetime.fromtimestamp(e.ctime[0])}.{e.ctime[1]}, modified: {datetime.fromtimestamp(e.mtime[0])}.{e.mtime[1]}")
print(f" metadata modified: {datetime.fromtimestamp(e.ctime[0])}.{e.ctime[1]}, modified: {datetime.fromtimestamp(e.mtime[0])}.{e.mtime[1]}")
print(f" device: {e.dev}, inode: {e.ino}")
print(f" user: {pwd.getpwuid(e.uid).pw_name} ({e.uid}) group: {grp.getgrgid(e.gid).gr_name} ({e.gid})")
print(f" flags: stage={e.flag_stage} assume_valid={e.flag_assume_valid}")
Expand Down Expand Up @@ -3262,7 +3262,7 @@ PATH is one or more file(s) to stage. The bridge is as boring as can be.
The main difference with =rm= is that =add= needs to create an index
entry. This isn't hard: we just =stat()= the file and copy the
metadata in the index's field (=stat()= returns those metadata the
index stores: creation/modification time, and so on)
index stores: metadata modification/modification time, and so on)

#+BEGIN_SRC python :tangle libwyag.py
def add(repo, paths, delete=True, skip_missing=False):
Expand Down