lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

On Mon, Jun 9, 2008 at 5:07 PM, David Kastrup <> wrote:
"RJP Computing" <> writes:

> On Mon, Jun 9, 2008 at 4:06 PM, David Kastrup <> wrote:
>     "RJP Computing" <> writes:
>     > OK. So far I don't see any Subversion access to Lua, so I think this
>     > makes my decision easy. git, bazaar, and Mercurial are all great. I
>     > don't want to offend anybody or start a discussion about what version
>     > control system to use. I just need Subversion access to the files. I
>     > am not an expert, but so far I can't find a way to use a
>     > Bazaar/git/Mercurial repository with an svn client.
>     Huh?  "git svn dcommit" will commit to SVN just fine.
> Yeah, I am talking about the other way around. Make a git repository
> and allow svn clients to commit and such.

Why?  Just import every tarball into git, and then push into the central
SVN repository everybody is going to work with.  git will reconstruct
the rename/move history and SVN will be glad to receive and exhibit it.
In short: just use git as your private toolkit in order to import new
versions into SVN.

I guess my brain can't understand what you are trying to say. :) If I can restate what I think you are saying is to make a git repository somewhere on the public internet. (I don't know of any free git hosts) Then use that as the external repository and then I import the git into our local svn repository.

If this is correct, I can't see any benefit. It actually makes it harder for the repository admin. If I just do the same suggestion, only use svn, I can use Subversions ability to include externals and just get the code directly from the internet svn repository.

Can you explain why that is better then using svn? And I am not talking about reasons one version control is better then the other. I am tring to understand why it matters if I use the philosophy of coping the tarball to a git repository or to a svn repository.
RJP Computing