Re: [Vim-latex-devel] Can I clone just the vimfiles directory?
There is a recent thread that is very similar to this. Look for the subject Merging vim-latex/master:vimfiles into local repo from Feburary 17 of this year. A key difference between DVCS (all of them) and subversion is that the change history is associated with an entire project and not with particular files or subdirectories, like you have in subversion. When designing the structure of the DVCS repository up front, there are ways to create subrepositories inside directories that can be treated in a similar way (i.e., instead of cloning vim-latex you clone vim-latex-vimfiles which is otherwise parked inside the vimfiles directory inside vim-latex), but that requires setting things up ahead of time. In that thread mentioned above, Till seems happy with splitting the vim-latex web and vimfiles into two separate projects. That would solve the problem. However, it was unresolved as to whether it would be better to generate two new repositories (e.g., with hg convert) with new changeset id's, or generate one totally new repository and just mutate the directory structure in the old repository to maintain the old change history. So it's possible in the future (near future?) the vim-latex repo will look very different and it may be possible to do more exciting things (like using a hg pull to pull the unrelated repository into your own vimfiles repository, and then merging your repo with the Mercurial repo). Meanwhile, it may be better to create your clone elsewhere and then use rsync to update files in your home directory. For example, from the vimfiles directory inside the vim-latex repo, you can do: make -f Makefile.in install and it will execute: rsync -CrtW --exclude='*~' --exclude='*.swp' --exclude='makefile' . ~/.vim which will copy any new vim-latex/vimfiles changes into ~/.vim. --Ted On 03/06/2011 10:15 PM, Jeremy Conlin wrote: I would like to stay abreast of the latest changes in vim-latex. That is, I would like my vimfiles to be current with what is available in the repository. I know the repository was recently changed from subversion to git. In subversion I could just checkout the vimfiles directory into my ~/.vim directory. I'm not sure how to do this with git. Is it possible to clone only the vimfiles directory ? -- 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
Re: [Vim-latex-devel] Can I clone just the vimfiles directory?
On Mon, Mar 07, 2011 at 02:37:30PM -0500, Ted Pavlic wrote: So it's possible in the future (near future?) the vim-latex repo will look very different and it may be possible to do more exciting things Yes, I hope to get to this in the near future. which will copy any new vim-latex/vimfiles changes into ~/.vim. Minimal testing showed me that it is also possible to clone the git repository somewhere outside the vim-directory and symlink to the vimfiles subdirectory inside the git repository from ~/.vim: $ cd $HOME $ git clone git://vim-latex.git.sourceforge.net/gitroot/vim-latex/vim-latex $ mv .vim .vim_old $ ln -s vim-latex/vimfiles/ .vim With git 1.7.4 on Fedora I can also use git commands inside ~/.vim. Regards Till pgpMPYK3Wor4F.pgp Description: PGP signature -- 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
Re: [Vim-latex-devel] Can I clone just the vimfiles directory?
On Mon, Mar 7, 2011 at 12:37 PM, Ted Pavlic t...@tedpavlic.com wrote: There is a recent thread that is very similar to this. Look for the subject Merging vim-latex/master:vimfiles into local repo from Feburary 17 of this year. A key difference between DVCS (all of them) and subversion is that the change history is associated with an entire project and not with particular files or subdirectories, like you have in subversion. When designing the structure of the DVCS repository up front, there are ways to create subrepositories inside directories that can be treated in a similar way (i.e., instead of cloning vim-latex you clone vim-latex-vimfiles which is otherwise parked inside the vimfiles directory inside vim-latex), but that requires setting things up ahead of time. In that thread mentioned above, Till seems happy with splitting the vim-latex web and vimfiles into two separate projects. That would solve the problem. However, it was unresolved as to whether it would be better to generate two new repositories (e.g., with hg convert) with new changeset id's, or generate one totally new repository and just mutate the directory structure in the old repository to maintain the old change history. So it's possible in the future (near future?) the vim-latex repo will look very different and it may be possible to do more exciting things (like using a hg pull to pull the unrelated repository into your own vimfiles repository, and then merging your repo with the Mercurial repo). Meanwhile, it may be better to create your clone elsewhere and then use rsync to update files in your home directory. For example, from the vimfiles directory inside the vim-latex repo, you can do: make -f Makefile.in install and it will execute: rsync -CrtW --exclude='*~' --exclude='*.swp' --exclude='makefile' . ~/.vim which will copy any new vim-latex/vimfiles changes into ~/.vim. --Ted On 03/06/2011 10:15 PM, Jeremy Conlin wrote: I would like to stay abreast of the latest changes in vim-latex. That is, I would like my vimfiles to be current with what is available in the repository. I know the repository was recently changed from subversion to git. In subversion I could just checkout the vimfiles directory into my ~/.vim directory. I'm not sure how to do this with git. Is it possible to clone only the vimfiles directory ? Thanks for the information. I looked at the previous discussion and think I will just wait until the repository is separated or subrepository is activated. In the meantime, I can be content to just make vim-latex to get the latest files. Jeremy -- 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
Re: [Vim-latex-devel] Can I clone just the vimfiles directory?
On Mon, Mar 7, 2011 at 3:20 PM, Till Maas opensou...@till.name wrote: On Mon, Mar 07, 2011 at 02:37:30PM -0500, Ted Pavlic wrote: So it's possible in the future (near future?) the vim-latex repo will look very different and it may be possible to do more exciting things Yes, I hope to get to this in the near future. which will copy any new vim-latex/vimfiles changes into ~/.vim. Minimal testing showed me that it is also possible to clone the git repository somewhere outside the vim-directory and symlink to the vimfiles subdirectory inside the git repository from ~/.vim: $ cd $HOME $ git clone git://vim-latex.git.sourceforge.net/gitroot/vim-latex/vim-latex $ mv .vim .vim_old $ ln -s vim-latex/vimfiles/ .vim This works fine unless I have other customization files (which I do) which reside in .vim. Thanks again, Jeremy -- 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
Re: [Vim-latex-devel] Can I clone just the vimfiles directory?
It looks like you can edit $GIT_DIR/info/sparse-checkouts to specify things that you don't want. You need to turn on core.sparseCheckout (e.g., in your .gitconfig) to turn this feature on though. I verified this... works... In .gitconfig: [core] sparseCheckout=1 Then: $ cd $HOME $ git clone git://vim-latex.git.sourceforge.net/gitroot/vim-latex/vim-latex $ echo vimfiles vim-latex/.git/info/sparse-checkout $ cd vim-latex $ git reset --hard $ ls # only vimfiles and .git show That's not quite like what you'd expect from SVN, but maybe you can do something with that... -- 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
