2014-05-09 3:13 GMT+02:00 Andy Bradford <amb-fos...@bradfords.org>:
> Also, I can commit if I do ``fossil status'' first:

That's the difference!: I use "fossil status" a lot, therefore I
didn't notice that the function unsaved_changes() doesn't
do anything when vid=0. This bug can be triggered
on trunk as well (although with fossil alone you cannot
create the situation that vid=0). Fixed on trunk now. Thanks!

Just did a "fossil new", a single "add", and this manifest
was created:
    C x.txt
    D 2014-05-09T07:30:20.956
    F x.txt a1db6bf2d7f484c7bb0c957eef08fb348de4632b
    R 6d1a3f680cad8c3911b58e8783e5215d
    T *branch * trunk
    T *sym-trunk *
    U nijtmaj
    Z 6f2cb303c3b860c3542d69b99a38b8f3
Looks good at first sight.

> But if I close/open the Fossil, the  file does not come back.

So let's close and open it

$ fossil open ../new.fossil
x.txt
project-name: <unnamed>
repository:   /Localdata/workspace/xxx/../new.fossil
local-root:   /Localdata/workspace/xxx/
config-db:    C:/Users/nijtmaj/AppData/Local/_fossil
project-code: 15fb36c9fc591186d91adc1e1a636c8845fe5aa5
checkout:     6c3b32f1d696a3db27127baf84f86100d48d29e2 2014-05-09 07:30:20 UTC
leaf:         open
tags:         trunk
comment:      x.txt (user: nijtmaj)
checkins:     1

$ fossil ls
x.txt


The file came back just fine.

I thought I fixed all situations in fossil where vid=0, but apparently
missed one.

2014-05-08 22:20 GMT+02:00 B Harder <brad.har...@gmail.com>:
> I restrained myself in the previous discussion that ended up being about the
> initial empty commit, but now I feel compelled: the rational, "discussion",
> and decision to remove the initial empty commit were pretty poor, IMO. I
> don't want to belabor the point, so I'll leave it at that.
>
> Happy to discuss or be corrected.

My impression is that the only reason for the presence of the initial empty
commit is that fossil cannot handle a repository without it. If there
is any other reason, please share that with us! I would like to give
people a choice: People who want it (e.g. for reasons of legacy) should
have it, people who don't expect it shouldn't be surprised by being
given one without being asked ;-)

Thanks!

Regards,
       Jan Nijtmans
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to