Every repository as an initial check-in which is empty. But it always has
a different SHA1 hash, since it also includes the timestamp from when the
repository was created. Example:
http://www.fossil-scm.org/fossil/info/a28c83647d
And the actual text of the manifest artifact:
http://www.fossil-scm.org/fossil/artifact/a28c83647dfa805f
On Fri, Dec 20, 2013 at 6:23 PM, David Given <d...@cowlark.com> wrote:
> hg has a concept of the changeset with uuid
> 0000000000000000000000000000000000000000. This is the empty changeset,
> and is equivalent to the parent of the very first checkin. Checking out
> this changeset will give you an empty repository; checking in with this
> as the parent will give you a new tree, not connected to the old one.
>
> I find myself needing to do this in Fossil: both as something I can
> check out to remove all files from the working directory, and something
> I can use as a parent so I can create multiple revision trees.
>
> AFAIK there's nothing in the Fossil architecture to forbid it --- is
> there any way I can do this?
>
> --
> ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
> │ "There does not now, nor will there ever, exist a programming
> │ language in which it is the least bit hard to write bad programs." ---
> │ Flon's Axiom
>
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
