posix: always seek to EOF when opening a file in append mode Python 3 already does this, so skip it there. Consider the program: #include <stdio.h> int main() { FILE *f = fopen("narf", "w"); fprintf(f, "narf\n"); fclose(f); f = fopen("narf", "a"); printf("%ld\n", ftell(f)); fprintf(f, "troz\n"); printf("%ld\n", ftell(f)); return 0; } on macOS, FreeBSD, and Linux with glibc, this program prints 5 10 but on musl libc (Alpine Linux and probably others) this prints 0 10 By my reading of https://pubs.opengroup.org/onlinepubs/009695399/functions/fopen.html this is technically correct, specifically: > Opening a file with append mode (a as the first character in the > mode argument) shall cause all subsequent writes to the file to be > forced to the then current end-of-file, regardless of intervening > calls to fseek(). in other words, the file position doesn't really matter in append-mode files, and we can't depend on it being at all meaningful unless we perform a seek() before tell() after open(..., 'a'). Experimentally after a .write() we can do a .tell() and it'll always be reasonable, but I'm unclear from reading the specification if that's a smart thing to rely on. This matches what we do on Windows and what Python 3 does for free, so let's just be consistent. Thanks to Yuya for the idea.

     1

running: init test1

     2

result: 0

     3

running: add foo

     4

result: 0

     5

running: commit -m commit1 -d 2000-01-01 foo

     6

result: 0

     7

running: commit -m commit2 -d 2000-01-02 foo

     8

result: 0

     9

running: log -r 0

    10

changeset:   0:0e4634943879

    11

user:        test

    12

date:        Sat Jan 01 00:00:00 2000 +0000

    13

summary:     commit1

    14

    15

result: 0

    16

running: log -r tip

    17

changeset:   1:45589e459b2e

    18

tag:         tip

    19

user:        test

    20

date:        Sun Jan 02 00:00:00 2000 +0000

    21

summary:     commit2

    22

    23

result: 0