On Thu, Feb 12, 2009 at 11:42 AM, Markus Heidelberg
markus.heidelb...@web.de wrote:
I know how to handle the separate extra and lang packages and that you
should be able to omit them, it's done so in Buildroot.
But my question was, why they exist in the first place instead of creating a
On Thu, Feb 12, 2009 at 11:39 PM, Markus Heidelberg
markus.heidelb...@web.de wrote:
note that my git repo on github is made of vim+extra into 1 product.
I did not include the lang package.
Oh, what was the reason?
disk space on github: I might reconsider :)
--
Christian
--
On Fri, Feb 13, 2009 at 4:18 AM, _sc_ tooth...@swbell.net wrote:
the moral of the story is: keep your updates to feature.h
invisible to git or he'll quit on you and you might easily
miss it
NO
Keep your own feature.h in a _dedicated_ branch. One thing you may
have not realized yet, is that
On Thu, Feb 5, 2009 at 10:23 PM, Markus Heidelberg
markus.heidelb...@web.de wrote:
Hi,
I've finally written a basic script (without any error handling so far)
for automatically fetching the patch files, applying, formatting the
commit message and committing to the vim_extended/vim_mainline
On Sat, Jan 24, 2009 at 4:05 PM, Markus Heidelberg
markus.heidelb...@web.de wrote:
it's not a bug, it's a feature (tm).
I can't find a feature. At least if there is one, then I don't like it.
But I can see the problems when creating a repo for Vim and your layout
with unrelated branches is
On Mon, Jan 26, 2009 at 10:58 AM, Markus Heidelberg
markus.heidelb...@web.de wrote:
ever tried git-cvsimport on the official vim repo ? you'll see it's
linear, and vim7 and vim7 are actually different CVS repositories.
No, I haven't tried this.
you'll need a few hours, if not a full half-day
On Mon, Jan 26, 2009 at 9:45 PM, Milan Vancura mi...@ucw.cz wrote:
5. what about a cooperation with Christian and pul his git tree as
vim_upstream? There is no dependency on svn, nice tags for vim versions
are
there... Would it be possible?
No, it wouldn't.
It looks nice at
On Tue, Jan 27, 2009 at 1:57 AM, Markus Heidelberg
markus.heidelb...@web.de wrote:
I asked Markus his requirements: his answers show a trend hard to
satisfy.
I'm not sure if I understand you correctly, but I don't see a problem in
satisfying my requirements. Or do you mean, we can't arrange
On 1/24/09, Bram Moolenaar b...@moolenaar.net wrote:
Christian Michon wrote:
I've a hunk failing in this patch, and actually other patches are
failing in this serie (I can post a detailed list).
I used in the past patch -p0 -s -t list_of_patch, but this time I
did not use the silent mode
On Fri, Jan 23, 2009 at 12:29 AM, Markus Heidelberg
markus.heidelb...@web.de wrote:
5. what about a cooperation with Christian and pul his git tree as
vim_upstream? There is no dependency on svn, nice tags for vim versions
are
there... Would it be possible?
No, it wouldn't.
It looks
I've a hunk failing in this patch, and actually other patches are
failing in this serie (I can post a detailed list).
I used in the past patch -p0 -s -t list_of_patch, but this time I
did not use the silent mode and now I can see real errors.
I used standard released tarballs.
Bram, is this
On Thu, Jan 22, 2009 at 1:06 AM, Markus Heidelberg
markus.heidelb...@web.de wrote:
Christian MICHON, 21.01.2009:
On Tue, Jan 20, 2009 at 5:39 PM, Milan Vancura mi...@ucw.cz wrote:
It would be nice to have a public branch at vim_extended. (I have that
branch
in my local git tree cloned
On Thu, Jan 22, 2009 at 10:51 AM, Markus Heidelberg
markus.heidelb...@web.de wrote:
Christian MICHON, 22.01.2009:
On Thu, Jan 22, 2009 at 1:06 AM, Markus Heidelberg
markus.heidelb...@web.de wrote:
Christian MICHON, 21.01.2009:
sending a git-bundle to a repo maintainer is actually better
On Tue, Jan 20, 2009 at 5:39 PM, Milan Vancura mi...@ucw.cz wrote:
I suggest you email the list with the full patch, asking to be included in
vim_extended -- that way, you get more testing for your patch will be able
to polish it even more if needed.
Hello Richard,
I already posted all
On Tue, Dec 23, 2008 at 3:39 AM, Markus Heidelberg
markus.heidelb...@web.de wrote:
quick feedback after a cloning of vim_mainline: tons of commits are
due to git-svn merged commits and syncing with CVS.
could this be avoided ? maybe some commits can be squashed.
Why should I squash only to
On Thu, Dec 18, 2008 at 11:26 AM, John Beckett johnb.beck...@gmail.com wrote:
I should take a little longer checking, but in view of the potential for
damage I'm sending a preliminary opinion:
A message has just been sent to the vim_multibyte list.
Header includes:
From:
Hi Bram, Developers,
I updated the git repo of vim on github. It now contains 7.2 up to
today's patches.
I'll update it every 50 patches more or less, depending on the patch frequency.
It's at the following URL:
http://github.com/cmichon/vim
For those who never used git, no worries:
- just
On Fri, Jul 4, 2008 at 2:12 AM, Markus Heidelberg
[EMAIL PROTECTED] wrote:
Keep in mind that:
- this is not upstream of course
With the only difference that it's inofficial, right?
exactly! the purpose is to keep an updated version, as accurate as
cvs/svn/tarballs+patches with correct dates
On Thu, Jul 3, 2008 at 1:12 PM, Henrik Öhman [EMAIL PROTECTED] wrote:
It's at the following URL:
http://github.com/cmichon/vim
[...]
Very pretty. :)
thanks! it's not my doing: the github interface design is cool indeed.
The commit messages seem to be slightly broken in that they have
On Tue, Jul 1, 2008 at 12:21 PM, Richard Hartmann
[EMAIL PROTECTED] wrote:
wget comes to mind. I am sure you will find a script to do what you
want. Wanting web archives in a sane format is not too uncommon,
after all.
thanks for suggesting it. as I mentioned, it would have been the last
On Mon, Jun 30, 2008 at 11:39 PM, James Vega [EMAIL PROTECTED] wrote:
One feedback: we should try to keep the patch numbers from Bram in the
shortlog, shouldn't we ?
*shrug* I went back and forth on that and ended up leaving it as is
since that's the way I started.
I managed to find a neat
On Mon, Jun 30, 2008 at 6:31 PM, Tony Mechelynck
[EMAIL PROTECTED] wrote:
The problem with patches is bit-rot. Scripts will usually remain valid,
even when unattended; patches must be cared for, or after some time they
won't apply anymore.
you can avoid bitrotting provided you can rebase
Hi Bram,
I'm consolidating the dates I extracted from the ftp server for the
git repo I'm creating, but I expect some of these dates to be off
versus the mailing list dates.
Is there somewhere where I could download mbox format of all vim-dev
messages since let's say version 6.0 ? Thanks in
On Mon, Jun 30, 2008 at 11:13 PM, Tony Mechelynck
[EMAIL PROTECTED] wrote:
See http://vim.sourceforge.net/maillist.php#vim-dev under Archive. I
don't know under what format the archives are held.
web based format, close to useless unless I write a clever awk script
after I individually
On Fri, Jun 27, 2008 at 7:00 PM, Tony Mechelynck
[EMAIL PROTECTED] wrote:
Oh the greatness of address book completion... In SeaMonkey (or
Thunderbird) hitting v in the To box gives me a rolldown menu of Vim
groups and I only have to select the right one. :-)
I'm surprised! I was expecting
Bram,
what is the unix command you use to generate your patches ?
(actually with their current format, they're not well accepted by git).
Thanks
--
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
On Fri, Jun 27, 2008 at 8:13 PM, James Vega [EMAIL PROTECTED] 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
On Thu, Jun 26, 2008 at 1:46 AM, John Beckett [EMAIL PROTECTED] wrote:
I use the FTP server to get patches (with a Python script - very easy), and I
apply
them manually (easy). So I have no personal interest in the CVS or SVN
distributions. However, lurking here has shown quite a bit of pain
On Thu, Jun 26, 2008 at 12:18 PM, Mike Williams
[EMAIL PROTECTED] wrote:
Sorry to rain on the git love fest going on but ...
There are other options. There is no killer reason to use git over the
other systems, and the need for a Cygwin base system for windows does
raise the bar for
On Thu, Jun 26, 2008 at 11:49 PM, björn [EMAIL PROTECTED] wrote:
I have nothing to add to this thread as a whole, but since it was
brought up let me just quickly comment on the MacVim.git repository.
All I am doing now is tracking the trunk of the svn repository which
turns out wasn't perhaps
On Wed, Jun 25, 2008 at 12:45 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Adding another system won't solve the CVS problems. Can't just drop CVS
right now, many people are using it.
I would not add it. I would use it to replace them all (I'm too
supportive with git, I know...)
using CVS
and if you use vim -X ?
On Wed, Jun 25, 2008 at 2:25 PM, Richard Hartmann
[EMAIL PROTECTED] wrote:
Hi all,
something that has irritated me for ages, but which I never thought
about in this way, is the fact that when you start vim on a console,
vim detects a X server running, vim tries to
On Tue, Jun 24, 2008 at 10:38 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Announcing: Vim (Vi IMproved) version 7.2a BETA
compiled successfully with uclibc-0.9.29 + gtk-1.2.10 on DetaolB.
Test results:
ALL DONE
nice work!
Thanks!
--
Christian
--
http://detaolb.sourceforge.net/, a linux
On Wed, Jun 25, 2008 at 2:00 AM, Bram Moolenaar [EMAIL PROTECTED] wrote:
There is something wrong with what CVS did to the files. Especially in
runtime/tutor. Might take a day to sort out.
Sigh. Why can't I just tell CVS that this is the tree of files I want
to have in the repository?
34 matches
Mail list logo
