git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Stricker <astricker@futurelab.ch>
To: schachtobi <schachtobi@web.de>
Cc: git@vger.kernel.org
Subject: Re: svn propset - focus on svn:externals
Date: Wed, 29 Sep 2010 10:12:05 +0200	[thread overview]
Message-ID: <4CA2F4D5.6010601@futurelab.ch> (raw)
In-Reply-To: <4C9115E9.4080900@web.de>

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

schachtobi wrote:
> * svn:externals (not yet supported? Found nothing so far)
>   except solutions here:
>
http://panthersoftware.com/articles/view/3/svn-s-svn-externals-to-git-s-submodule-for-rails-plugins
>   but this is not the same since the client has to setup the links,
> repositories etc. And they do not come automatically as in subversion.

Then there is also the git-svn-clone-externals [1]

>   I guess submodules is the proper replacement. But still having the
> svn:externals from a pull this could be done automatically without the
> need for scripting. And the dcommit should also work for the submodules.

Git submodules could help here, but I doubt there is a full automated
solution that will work in all circumstances. Here at work we have an
excessive use of svn:externals that points diagonally through the whole
repository.

> for me the svn:merginfo and the svn:externals would be most benifitial
> since our team uses this a lot and without being able to set those from
> git it will be not possible for me to use git for a svn client to do the
> merges.

For me the support for the new svn:externals syntax [2] would be a first
huge step forwards. With the proper support for the new syntax I may use
the git-svn-clone-externals [1] to fetch the externals.

I started to extend git-svn to support those new syntax and pushed
it to github [3] for those who are interested. I'm a bit busy at the
moment, but like to continue this work.

Regards, Andy

[1] http://github.com/andrep/git-svn-clone-externals
[2] http://subversion.apache.org/docs/release-notes/1.5.html#externals
[3] http://github.com/AndyStricker/git#



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4722 bytes --]

      reply	other threads:[~2010-09-29  8:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 18:52 svn propset schachtobi
2010-09-29  8:12 ` Andreas Stricker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CA2F4D5.6010601@futurelab.ch \
    --to=astricker@futurelab.ch \
    --cc=git@vger.kernel.org \
    --cc=schachtobi@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).