> With Subversion, you can have unversioned files inside of a versioned
> directory. When updating to the latest files in the repository, the
> unversioned files were untouched. I would hope this would be the same
> with git. Otherwise, this whole idea of keeping my ~/.vim updated to
> the vim-latex/vimfiles is a moot point.
In git (as with all DVCS), versioning exists at the project level and
not the file level. You could certainly put unmanaged files within a git
repository and never add them to the change history, but the first time
you do something like 'git reset --hard' (or a similar checkout), the
files you added would be in danger of being removed by git.
The ideal situation would be to manage your ~/.vim directory in git and
then merge a vimfiles repository from vim-latex into your .vim
directory. That way you could pull vim-latex updates into your change
history and then merge them ("git pull" provides a way to automate
fetching and merging). Unfortunately, with the git repo having a
vimfiles /subdirectory/, it is a little more complicated.
It's possible that a local changeset on your side that moves everything
from /vimfiles/ into the root directory and then gets rid of the web
files might do the trick. That is, the merge with your local history
should (I think?) "re-move" and "re-delete" every time. It's worth a
shot (in a test ~/.vim directory), but it would be much easier if the
vim-latex git repo looked like a vimfiles directory.
--Ted
--
Ted Pavlic <t...@tedpavlic.com>
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
