From: "Eddy Petrișor" <eddy.petrisor@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 0/3] git-svn-externals PoC (in a sh script)
Date: Fri, 29 Aug 2008 03:16:00 +0300 [thread overview]
Message-ID: <60381eeb0808281716l512a4ac5kc7ba41c0d00e6baa@mail.gmail.com> (raw)
In-Reply-To: <60381eeb0808281702q3dc7543enff2b35ebbcc80d08@mail.gmail.com>
Please CC me, I am not listed.
2008/8/29 Eddy Petrișor <eddy.petrisor@gmail.com>:
> Hello,
>
> I have started a while back working on support for svn:externals
> support for git-svn, but since I'm not that satisfied with the current
> status of the patch, I haven't modified git-svn itself and just left
> the sh script I made as a PoC as it was.
>
> There's still work to be done to it, but I the current version is
> functional enough to be probably found useful by more people than
> myself.
>
>
> Current status follows:
>
> Current functionality:
> - fetches all the externals of an already svn-fetched repo
> - support for svn:externals refresh
> - if the location of the external has changed, the current working
> copy will be placed aside and a new directory will be created
> instead
> - if the remote URI is the same (maybe a verison bump, there will
> be a 'git svn rebase'
> - remove support (useful for testing purposes or clean restarts)
> - avoid zombie externals at all costs - in some repos empty
> svn:externals might exist; svn ignores such externals, so git should
> do the same
>
> TODO:
> - take into account the revision of an external, if it exists
> - do not do deep svn cloning, to avoid legthy operations, just pull HEAD
> (this actually needs changes in git-svn itself)
> - use/create shallow copies to git svn repos (one revision should be enough
> for most externals)
> - use submodules for externals
>
>
>
>
> Any comments are welcome.
>
>
> --
> Regards,
> EddyP
> =============================================
> "Imagination is more important than knowledge" A.Einstein
>
--
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein
next prev parent reply other threads:[~2008-08-29 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 0:02 [PATCH 0/3] git-svn-externals PoC (in a sh script) Eddy Petrișor
2008-08-29 0:02 ` [PATCH] git svn: should not display zombie externals Eddy Petrișor
2008-08-29 0:02 ` [PATCH] First crude implementation of git-svn-externals Eddy Petrișor
2008-08-29 0:02 ` [PATCH] added a test frame for git-svn-externals.sh Eddy Petrișor
2008-08-29 0:16 ` Eddy Petrișor [this message]
2008-08-29 9:29 ` [PATCH 0/3] git-svn-externals PoC (in a sh script) Eric Wong
2008-09-01 6:20 ` RFH: git-svn and submodules Eric Wong
2008-09-10 13:56 ` [PATCH 0/3] git-svn-externals PoC (in a sh script) Eddy Petrișor
2008-09-10 13:59 ` Eddy Petrișor
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=60381eeb0808281716l512a4ac5kc7ba41c0d00e6baa@mail.gmail.com \
--to=eddy.petrisor@gmail.com \
--cc=git@vger.kernel.org \
/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).