Hi Mateusz, hi Julien, hi Etienne,
Il 23/10/2011 02:41, Mateusz Łoskot ha scritto:
> 2011/10/22 Mateusz Łoskot :
>> 2011/10/21 Mateusz Łoskot :
>>> On 21 October 2011 07:54, Antonio Valentino
>>> wrote:
It seems that the svn2git [1] tool (based on git-svn) is able to import
svn reposito
2011/10/22 Mateusz Łoskot :
> 2011/10/21 Mateusz Łoskot :
>> On 21 October 2011 07:54, Antonio Valentino
>> wrote:
>>> It seems that the svn2git [1] tool (based on git-svn) is able to import
>>> svn repositories with branches in a proper way.
>>> I never used it an I don't know if it allows to pus
2011/10/21 Mateusz Łoskot :
> On 21 October 2011 07:54, Antonio Valentino
> wrote:
>> It seems that the svn2git [1] tool (based on git-svn) is able to import
>> svn repositories with branches in a proper way.
>> I never used it an I don't know if it allows to push changes back to
>> svn.
>> Anyway
>From this page it seems like it's quite easy using just "git svn", and
doesn't require an extra tool.
http://trac.parrot.org/parrot/wiki/git-svn-tutorial
Instructions there are:
git svn clone -s -r 4:HEAD https://svn.parrot.org/parrot # choose
some recent-ish commit
-s is for --stdlayout w
On 21 October 2011 07:54, Antonio Valentino
wrote:
> It seems that the svn2git [1] tool (based on git-svn) is able to import
> svn repositories with branches in a proper way.
> I never used it an I don't know if it allows to push changes back to
> svn.
> Anyway since Julien only needs to generate
Antonio,
It seems that the svn2git [1] tool (based on git-svn) is able to import
svn repositories with branches in a proper way.
I never used it an I don't know if it allows to push changes back to
svn.
Anyway since Julien only needs to generate a patch, svn2git should be
good for its purposes.
Hi Mateusz, hi Julien,
Il giorno Thu, 20 Oct 2011 21:59:27 +0100
Mateusz Łoskot ha scritto:
> 2011/10/20 Julien Malik :
> > Sorry I think I was not clear enough : my goal is to generate a
> > patch for inclusion in a gdal-1.8.0 debian package [1]
> > No plan at all for committing it in the gdal
2011/10/20 Julien Malik :
> Sorry I think I was not clear enough : my goal is to generate a patch for
> inclusion in a gdal-1.8.0 debian package [1]
> No plan at all for committing it in the gdal svn after that.
>
> I would play with my local git repo (letting git do all the hard work, I
> hope) an
Hi,
I just found myself in need for backporting one trunk commit into the 1.8
branch.
Of course extracting the diff and trying to apply it as-is does not work.
Git would certainly be my friend here (specifically git-rebase).
I'm afraid you'd need to extend the Git workflow on your own.
Once you'
2011/10/20 Julien Malik :
> Is it possible and/or planned that you also provide the gdal branches in git?
I guess it is possible. I just didn't bother to do it.
> I may be wrong but I only see the trunk.
You are correct. It' s only the trunk.
> I just found myself in need for backporting one tr
Hi,
Is it possible and/or planned that you also provide the gdal branches in
git ?
I may be wrong but I only see the trunk.
I just found myself in need for backporting one trunk commit into the
1.8 branch.
Of course extracting the diff and trying to apply it as-is does not work.
Git would ce
Hi,
To those who are interested, I've just posted updated pre-loaded [1] git
repository of GDAL which is a copy of what I use to maintain at GitHub [2]:
http://mateusz.loskot.net/tmp/gdal/mloskot-github-gdal-20111018.7z
[1] http://lists.osgeo.org/pipermail/gdal-dev/2011-October/030369.html
[2] h
12 matches
Mail list logo
