2015-03-18 18:41 GMT+01:00 Richard Hipp <d...@sqlite.org>:
> Perhaps the right way to handle this case is to modify
> https://www.fossil-scm.org/fossil/info/2e4de226a7?ln=1066-1110 so that
> if
>
> (1) The operation is "push", and
> (2) There is exactly one entry in the BLOB table, and
> (3) That one BLOB entry is a manifest
>
> Then it will overwrite the PROJECTCODE and "DELETE FROM blob; DELETE
> FROM plink; DELETE FROM event;" before proceeding.  (The SERVERCODE is
> an historical artifact that is no longer used for anything and can be
> safely ignored.)  This would permit any repository to push into a
> freshly created repo and the freshly created repo would take on the
> identity of the repository that is doing the push.

I like this idea. Thanks!

Regards,
        Jan Nijtmans
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev

Reply via email to