Steven Walter wrote:
That said, I'm not sure that stgit will help you with "local versioning" of files (I'm not even sure what you mean). Perhaps you can elaborate on this point.
He wants to create some files in his git-svn clone and use git to manage them -- checkpointing his work in progress, backing out changes, etc., without publishing those files to the svn repository. The files in question are not already in svn. But he does want to work on other files that *are* in the svn repository, and wants those changes to be committed back.
So my assumption was that he would do something like maintain his local-only changes as StGIT patches that never get committed to git. His other changes would get committed from StGIT to git, and from there he'd do his normal git-svn dcommit. Or maybe git-svn dcommit followed by stg rebase since git-svn dcommit creates new revision IDs.
In any event, now that I know it's working successfully for at least one person, I'll point him to stg and he can play with it a bit. Didn't want to lead him into a dead end. Thanks!
-Steve - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
