On 12/02/09 11:42, Markus Heidelberg wrote:
> Tony Mechelynck, 12.02.2009:
>> On 11/02/09 03:35, Markus Heidelberg wrote:
>>> But why this "extra" and the distinction between Unix and non-Unix at all?
>>>
>>> Markus
>> Because if you are on a Unix-like OS, you can get a functional Vim by
>> omitti
Christian MICHON, 13.02.2009:
>
> On Thu, Feb 12, 2009 at 11:39 PM, Markus Heidelberg
> 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 :)
On Thu, Feb 12, 2009 at 11:39 PM, Markus Heidelberg
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
--
http://detaolb.sourceforge.net/,
Christian MICHON, 12.02.2009:
>
> On Thu, Feb 12, 2009 at 11:42 AM, Markus Heidelberg
> 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
On Thu, Feb 12, 2009 at 11:42 AM, Markus Heidelberg
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
> single package. It m
Tony Mechelynck, 12.02.2009:
>
> On 11/02/09 03:35, Markus Heidelberg wrote:
> > But why this "extra" and the distinction between Unix and non-Unix at all?
> >
> > Markus
>
> Because if you are on a Unix-like OS, you can get a functional Vim by
> omitting everything that's not for Unix, includi
On 11/02/09 03:35, Markus Heidelberg wrote:
> James Vega, 06.02.2009:
>> On Thu, Feb 05, 2009 at 10:23:33PM +0100, Markus Heidelberg wrote:
>>> What do you think about the commit message format, is it ok? I searched
>>> for a git-like message, without losing information. The duplicated first
>>> l
Markus Heidelberg, 11.02.2009:
>
> Christian MICHON, 06.02.2009:
> > you're facing the same problem I faced in July. I noticed (example
> > 7.2.102) the commit message is truncated. so we're even here: I've the
> > same issue and this requires somehow manual intervention. :(
>
> James does manua
James Vega, 06.02.2009:
> On Thu, Feb 05, 2009 at 10:23:33PM +0100, Markus Heidelberg wrote:
> > What do you think about the commit message format, is it ok? I searched
> > for a git-like message, without losing information. The duplicated first
> > line of the problem description is unavoidable I
Christian MICHON, 06.02.2009:
>
> On Thu, Feb 5, 2009 at 10:23 PM, Markus Heidelberg
> wrote:
> >
> > What do you think about the commit message format, is it ok? I searched
> > for a git-like message, without losing information. The duplicated first
> > line of the problem description is unavoi
On Thu, Feb 5, 2009 at 10:23 PM, Markus Heidelberg
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 git
> repositories.
On Thu, Feb 05, 2009 at 10:23:33PM +0100, Markus Heidelberg wrote:
> What do you think about the commit message format, is it ok? I searched
> for a git-like message, without losing information. The duplicated first
> line of the problem description is unavoidable I think, because it
> should be fu
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 git
repositories. So from now on these repositories are no longer based on
the official s
13 matches
Mail list logo
