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
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/vimfile
On Mon, Mar 7, 2011 at 12:37 PM, Ted Pavlic 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
> chang
On Mon, Mar 7, 2011 at 3:20 PM, Till Maas 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 n
> 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
