When building in a git checkout, but from a system lacking git, it
is useful to fall back to the version determined when the git
checkout was last used from a system sporting git.
* build-aux/git-version-gen: Add support for the new option --fallback,
which comes into play when there is no $tarbal
* top/maint.mk (no-submodule-changes, public-submodule-commit): Quietly
proceed if git is not present.
Copyright-paperwork-exempt: yes
Signed-off-by: Peter Rosin
---
top/maint.mk |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/top/maint.mk b/top/maint.mk
index 93c25
>> Sure thing, I also rebased them while at it...
>
> ...but forgot the script-version. v4 coming up.
>
> Sorry for the noise.
But sent the wrong patch anyway and also omitted the subject.
*blush*
v5 coming up.
Cheers,
Peter
On 2012-12-28 02:35, Paul Eggert wrote:
> On 12/27/2012 03:41 PM, Peter Rosin wrote:
>> If it helps I can regenerate with your redirection fix, but I assume
>> whoever commits it can fix that part easily enough. Just let me know.
>
> How about if you do that, and we give Eric and/or others a week
* top/maint.mk (no-submodule-changes, public-submodule-commit): Quietly
proceed if git is not present.
Copyright-paperwork-exempt: yes
Signed-off-by: Peter Rosin
---
top/maint.mk |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/top/maint.mk b/top/maint.mk
index 93c25
When building in a git checkout, but from a system lacking git, it
is useful to fall back to the version determined when the git
checkout was last used from a system sporting git.
* build-aux/git-version-gen: Add support for the new option --fallback,
which comes into play when there is no $tarbal
When building in a git checkout, but from a system lacking git, it
is useful to fall back to the version determined when the git
checkout was last used from a system sporting git.
* build-aux/git-version-gen: Add support for the new option --fallback,
which comes into play when there is no $tarbal
* top/maint.mk (no-submodule-changes, public-submodule-commit): Quietly
proceed if git is not present.
Copyright-paperwork-exempt: yes
Signed-off-by: Peter Rosin
---
top/maint.mk |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/top/maint.mk b/top/maint.mk
index 93c25
> Sure thing, I also rebased them while at it...
...but forgot the script-version. v4 coming up.
Sorry for the noise.
Cheers,
Peter
Le 28 déc. 2012 à 14:48, Gary V. Vaughan a écrit :
> The latest version can, however, be dropped directly into the override
> directory, and will upgrade itself from changes to the override module
> sources:
>
> ┌─┤gary@anungunrama│~/Devo/libtool--devo--0│master│9f2b41f│
> ├!35
Le 28 déc. 2012 à 17:56, Paul Eggert a écrit :
> On 12/28/2012 03:02 AM, Akim Demaille wrote:
>> So here is my proposal.
>
> Looks good to me, thanks.
Pushed.
On Fri, Dec 28, 2012 at 09:08:39AM -0800, Paul Eggert wrote:
> On 12/28/2012 05:29 AM, Ondřej Bílka wrote:
> >Initialy I examined gnulib one but it uses hash tables and is hard to
> >inline so I wrote faster variant.
>
> Where is the faster variant?
Below. I fixed few details since first submiss
On 12/28/2012 05:29 AM, Ondřej Bílka wrote:
Initialy I examined gnulib one but it uses hash tables and is hard to
inline so I wrote faster variant.
Where is the faster variant? Should/could it be merged into gnulib?
On 12/28/2012 03:02 AM, Akim Demaille wrote:
So here is my proposal.
Looks good to me, thanks.
Salut Akim!
On 28 Dec 2012, at 19:22, Akim Demaille wrote:
> Le 28 déc. 2012 à 12:39, "Gary V. Vaughan" a écrit :
>> On 28 Dec 2012, at 18:00, Akim Demaille wrote:
>>> Can't all these bootstraps be merged? Bison used to have a forked
>>> one too, but Joel's and Jim's efforts resulted Bison's u
Le 28 déc. 2012 à 12:39, "Gary V. Vaughan" a écrit :
> On 28 Dec 2012, at 18:00, Akim Demaille wrote:
>> Le 28 déc. 2012 à 10:35, "Gary V. Vaughan" a écrit :
>>> Salut Akim!
>>
>> Hi Gary! Long time no see :)
>
> Too long! :)
Agreed :)
>> Can't all these bootstraps be merged? Bison used
On 28 Dec 2012, at 18:00, Akim Demaille wrote:
> Le 28 déc. 2012 à 10:35, "Gary V. Vaughan" a écrit :
>> Salut Akim!
>
> Hi Gary! Long time no see :)
Too long! :)
>> My bootstrap rewrite (used by Libtool & Zile among others) has always
>> passed any `--force' from it's own command line along
Le 27 déc. 2012 à 17:45, Paul Eggert a écrit :
> On 12/27/2012 02:25 AM, Akim Demaille wrote:
>> Is there a reason not to pass --force?
>
> I can't think of one.
So here is my proposal. The only observed difference is indeed ylwrap.
(And the early arrival of 2013 in some copyright notices due
Le 28 déc. 2012 à 10:35, "Gary V. Vaughan" a écrit :
> Salut Akim!
Hi Gary! Long time no see :)
> My bootstrap rewrite (used by Libtool & Zile among others) has always
> passed any `--force' from it's own command line along to all autoreconf
> and libtoolize invocations it makes without any p
Salut Akim!
On 27 Dec 2012, at 17:25, Akim Demaille wrote:
> I recently realized that I was stuck with an old ylwrap. I
> thought that bootstrap was appropriately upgrading my environment
> when a newer Automake was installed, but it is not the case, as
> bootstrap reads:
>
> # Tell autoreconf
20 matches
Mail list logo
