Hi,
I tried to fetch the git repository from spip and got a few problems:
- First one, if I fetch with
git clone http://git.spip.org/spip.git/
I get only tags up to spip-3.0.13 (but on the website they go up to
3.0.16). If I do it from the github repository it goes to 3.0.16 as
expected.
- Second, the squelettes-dist and plugins-dist are not fetched. If I try
to do it with the svn, they are fetched separately. But this doesn't
happen with git and no information is given about that on the wiki page
Do you have an idea why the repository is incomplete, and how do you
usualy proceed when you work with git?
Hi,
I tried to fetch the git repository from spip and got a few problems:
- First one, if I fetch with
git clone http://git.spip.org/spip.git/
I get only tags up to spip-3.0.13 (but on the website they go up to
3.0.16). If I do it from the github repository it goes to 3.0.16 as
expected.
- Second, the squelettes-dist and plugins-dist are not fetched. If I try
to do it with the svn, they are fetched separately. But this doesn't
happen with git and no information is given about that on the wiki page
I tried to fetch the git repository from spip and got a few problems:
- First one, if I fetch with
git clone http://git.spip.org/spip.git/
I get only tags up to spip-3.0.13 (but on the website they go up to
3.0.16). If I do it from the github repository it goes to 3.0.16 as
expected.
Thanks for you report. I check our sever configuration
http or git access target same repository. Then no reason to have a
difference in tags list.
- Second, the squelettes-dist and plugins-dist are not fetched. If I try
to do it with the svn, they are fetched separately. But this doesn't
happen with git and no information is given about that on the wiki page
Maybe we are missing an external init or somethig like that. I hope Camille
can provide you more infos about that
It's not a bug it's a feature
Actually we can't synchronize svn:external data. For at least two reasons :
-* git-submodule is not as svn:external, since git 1.8 is more closed
but not same.
-* plugins-dist have a tree structure different relative to others
plugins tree (not in an unique directory)
It's in my todo list, but not to now.
The idea will be to provide a specific repository with all submodules
plugins, but first I must resolve some problems with plugins-dist
projects.
Yes as alternative subtree exists, now difference between submodule
and subtree is less important than one year ago. We can follow any
branch now, and not only a commit.
But in each case it's incompatible with this precept : "don't broke
svn behaviour"
Then if a sutree/sumodul is adderd, svn:external must be also created
and on other way also.
Purpose is to add a new service and not replace it. Then it's a bit
more complicated
