> On 11/24/2016 04:56 AM, Uwe Brauer wrote: > I'm unclear on what you want to have happen. dir1 and dir2 are > checkouts of the same repo? If you want their contents to be > identical, why not symlink dir2 to dir1? If you want the contents to > be different, then why link an individual file? Some nuance is > escaping me.
Ok some background information then. The file in question is a so called bibtex file, a bibliographic database for all my latex files, called bibgraf.bib. It is placed in $HOME/bib ($HOME/bib/bibgraf.bib) and is under HG control. In other words this file is placed in its own repo. I use this file in most of my latex files, which are located in different directories. To do that no hard nor soft link is necessary. If appropriate paths are set latex knows about this file. However I have now a new directory say $HOME/publications/newresult newresult is now a different repo, contains various latex files and I pushed it to bitbucket for collaboration. I would like also to include, somehow, the bibgraf.bib file in the sense that it is pushed and pulled to the bitbucket repo. $HOME/publications/newresult/bibgraf.bib But now I have a problem. I have two different repos with the «same» file in it. Of course I could from time to time merge these two files manually and commit them to there respective repos, but I find this solution cumbersome, that is why I thought of using hardlinks. But hardlinks do not work, when I use hg update they are broken. > Do you want to be able to modify the files from either directory? yes > If > so, then do you want the last modification to be in effect in both > directories? yes > Is there a situation where you would want them to differ? no _______________________________________________ Mercurial mailing list Mercurial@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial
