2015-04-20 23:00 GMT+02:00 Warren Young w...@etr-usa.com:
It’s a bug in the #includes at the top of src/comformat.c. The following
trivial patch fixes it:
Patch applied:
http://fossil-scm.org/index.html/info/d32ca5928223a448
I have not checked whether this patch causes a portability
On Tue, 21 Apr 2015 11:09:05 +0200, Jan Nijtmans jan.nijtm...@gmail.com
wrote:
2015-04-21 10:24 GMT+02:00 Michael Richter ttmrich...@gmail.com:
The key wording there is within the repository tree.
It doesn't change the file system, only the naming of the files, etc.
in the
repository.
2015-04-21 10:24 GMT+02:00 Michael Richter ttmrich...@gmail.com:
The key wording there is within the repository tree.
It doesn't change the file system, only the naming of the files, etc. in the
repository. Whether this is desired or correct behaviour is … an area of
frequent discussion.
Hello,
I have been maintaining git mirrors of the fossil repositories of my
personal projects, so that they can be more easily found (on github)
and/or cloned. Here is the snipped of shell script I use to build the
git mirror repository:
cd ${GIT_REPO}
git init
fossil export --git -R
The key wording there is *within the repository* tree.
It doesn't change the file system, only the naming of the files, etc. in
the repository. Whether this is desired or correct behaviour is … an area
of frequent discussion.
My own response to that discussion is to use the fsl wrapper (
I’m aware of the “within the repository”, and actually I’m not among those who
are so interested in this changing this, as proposed by others. So, not the
same issue here.
What I’m reporting is unrelated to changes happening on disk. If you run the
example below you should not be allowed to
On Tue, Apr 21, 2015 at 5:27 AM, Natacha Porté nata...@instinctive.eu
wrote:
So to make it short, the fossil repository is a prefix of what the git
mirror currently is, with the extra git nodes being generated by git.
Is there any way to backport the git commits into the fossil repository
7 matches
Mail list logo
