Hi there, On Thu, Mar 26, 2015 at 09:32:32AM -0400, Manuel Ortega wrote: > On Thu, Mar 26, 2015 at 12:43 AM, Dominique Pellé <[email protected] > wrote: > > Manuel Ortega <[email protected]> wrote: > > or find out when a piece of code was changed and why. > Bram can (and should) put older parts under github.com/vim/70 and > github.com/vim/71, and then anyone who wants to go spelunking back in time > can still do so.
usually a nice way of working that out is to use some branch-release strategy. Basically, when you're working towards version N: - you use a branch `devel-N`, - then when it's ready for freeze-time, you branch it as `freeze-N` - then when it's ready for release you squash all the commits of the branch within the release branch - then you fork the release branch towards `devel-N+1` and start over that way, when you want to get the release branch you just git clone (or fork) the `release` branch (or master or whatever the name you give it) but not the other ones. Until you don't fetch older branches, you're all set. That was just for the "getting all history" point. I still believe that vim's history is not huge, and shouldn't be an issue. Just get mozilla's sources and there you'll get some fun :-) my 2 cents, -- Guyzmo -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
