push content of a symbolic link to remote server.

[Uwe Brauer]

   > Uwe Brauer <oub at mat.ucm.es> writes:


   > Please do take the advice and use a thin shell repo. Anything else
   > brings not-to-be-underestimated amounts of pain on the long run (I have
   > some normal repos with subrepos, and I would not do that again; the thin
   > shell prevents tight coupling of the history which would bite you at
   > some point, and be it when you try to upload your stuff to infocalypse
   > repositories for anonymous access and realize that an update will
   > trigger a request to the clearnet).

Well right now I still have difficulties grasps his logic.
I have

repo1/textfile
repo2/textfile
repo3/textfile
repo4/libraryfile

Now the library file is needed by repo1, repo2, and repo3.

So I thought push all of them to bitbucket and set
in repo1  .hgsub
repo4 = ../repo4
and clone repo4 insider repo1.

This is not the thin-shell approach, but I don't see which files I
should add in the main directory. But as I said I don't gasp still the
thin shell approach.

Uwe