I'm surprised no one has mentioned the approach of placing empty files in
the directory. If I had an empty folder (e.g. bin) I would:
touch bin/PlaceExecutablesHere
fossil add bin/PlaceExecutablesHere
and the empty file would keep that folder in the repository.
Every time I use fossil mv/rm, I've always had to issue the corresponding
mv/rm command (or equivalent commands in Windows). Can someone describe a
case where one would want to call fossil mv/rm, without intending the
referenced file to be moved/removed as well? To me, making fossil mv/rm
perform
Seen with Fossil 1.29, and reproduced
with b0febccc4e1cf5c6763e3aa088b1ea788d255e47 (2015-02-24 06:03:54).
Summary:
I created a new branch, and in the new branch:
- Committed a rename of file A to B.
- Committed an add of a new file A.
- Committed changes to files A and B.
Then I merged the
Richard Hipp wrote about this before:
https://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg11761.html
His reponse in that link:
The pull and sync are requesting and receiving all SHUN records. You can
disable this using
fossil setting auto-shun off
On Sun, Jul 6, 2014
I have two versions of my repository that I've saved from a while ago, the
last time I ran into this syncing issue. I've linked them both here, hoping
that someone can analyze them and figure out what the issue is. In this
case, the artifact not being synced is a new branch commit (see commit
to be fixed. Though --verily looks
promising.
Donny Ward
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
6 matches
Mail list logo
