On Fri, Jun 27, 2008 at 11:57:33AM -0700, Gautam Iyer wrote: > On Fri, Jun 27, 2008 at 02:50:48PM -0400, James Vega wrote: > > >>> For the "upstream" branch I maintain in my git repository for the Debian > >>> package, I have a script which simply applies Bram's patches with the > >>> patch command and then constructs commit messages based on the short > >>> description from the README file on the ftp server and the block > >>> description in the actual patch. > >>> > >> yes, this is what I do too (for many years). It's frustrating to find > >> out git does not swallow all types of patches. > >> > >> Thanks for the explanations. Apparently, we use a similar approach to > >> build a git repo. Is yours already available somewhere ? > > > > Yes, it's available at git.debian.org[0]. update-patches[1] is the script I > > use. Lines 55-65 are the parts that update the upstream branch and the rest > > is just to ease the process of keeping the Debian branches updated. > > > > [0] - http://git.debian.org/?p=pkg-vim/vim.git > > [1] - > > http://git.debian.org/?p=pkg-vim/vim.git;a=blob;f=debian/update-patches;hb=HEAD > > Any chance we can update the downloads section on www.vim.org to provide > a link to this? (I see you have an "upstream" branch, so that non-debian > users can get the vanilla sources if they so desire.)
I only update the upstream branch when I get around to working on the package, though, instead of as Bram releases patches. It's not uncommon for me to be 10-20 patches behind. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
