Re: [PATCH v4 2/2] git-version-gen: add --fallback option to use if git is not present

Hi Eric, Thanks for the push! On 2012-12-31 23:45, Eric Blake wrote: > On 12/28/2012 03:13 PM, Peter Rosin wrote: >> 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 la

[PATCH v5 2/2] git-version-gen: add --fallback option to use if git is not present

$tarball_version_file and git is not working. (scriptversion): Update. Copyright-paperwork-exempt: yes Signed-off-by: Peter Rosin --- build-aux/git-version-gen |9 +++-- 1 files changed, 7 insertions(+), 2 deletions(-) diff --git a/build-aux/git-version-gen b/build-aux/git-version-gen index

[PATCH v5 1/2] maint.mk: handle missing git with more grace

* 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

Re: git-version-gen w/o git

>> 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

Re: git-version-gen w/o git

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

[PATCH v3 1/2] maint.mk: handle missing git with more grace

* 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

[PATCH v3 2/2] git-version-gen: add --fallback option to use if git is not present

$tarball_version_file and git is not working. (scriptversion): Update. Copyright-paperwork-exempt: yes Signed-off-by: Peter Rosin --- build-aux/git-version-gen |9 +++-- 1 files changed, 7 insertions(+), 2 deletions(-) diff --git a/build-aux/git-version-gen b/build-aux/git-version-gen index

[PATCH v4 2/2] git-version-gen: add --fallback option to use if git is not present

$tarball_version_file and git is not working. (scriptversion): Update. Copyright-paperwork-exempt: yes Signed-off-by: Peter Rosin --- build-aux/git-version-gen |9 +++-- 1 files changed, 7 insertions(+), 2 deletions(-) diff --git a/build-aux/git-version-gen b/build-aux/git-version-gen index

[PATCH v4 1/2] maint.mk: handle missing git with more grace

* 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

[no subject]

> Sure thing, I also rebased them while at it... ...but forgot the script-version. v4 coming up. Sorry for the noise. Cheers, Peter

Re: git-version-gen w/o git

On 2012-12-24 03:05, Paul Eggert wrote: > On 11/29/2012 11:12 PM, Peter Rosin wrote: >> This seems to be stalled because of a misconception. Can I please get >> a second opinion? Please? > > I'm afraid I don't understand the problem well enough to offer > an opi

Re: git-version-gen w/o git

On 2012-11-13 15:32, Peter Rosin wrote: > On 2012-10-18 15:56, Peter Rosin wrote: >> Hi Eric! >> >> On 2012-10-18 15:02, Eric Blake wrote: >>> [adding-gnulib] >> >> I'm not subscribed, please (continue to) keep me in CC. >> >>> On 10/

Re: git-version-gen w/o git

On 2012-10-18 15:56, Peter Rosin wrote: > Hi Eric! > > On 2012-10-18 15:02, Eric Blake wrote: >> [adding-gnulib] > > I'm not subscribed, please (continue to) keep me in CC. > >> On 10/18/2012 06:50 AM, Peter Rosin wrote: >>> Hi! >>> >>

[PATCH 2/2] git-version-gen: add --fallback option to use if git is not present

$tarball_version_file and git is not working. (scriptversion): Update. Copyright-paperwork-exempt: yes Signed-off-by: Peter Rosin --- build-aux/git-version-gen |9 +++-- 1 files changed, 7 insertions(+), 2 deletions(-) diff --git a/build-aux/git-version-gen b/build-aux/git-version-gen index

[PATCH 1/2] maint.mk: handle missing git with more grace

* 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

Re: git-version-gen w/o git

Hi Eric! On 2012-10-18 15:02, Eric Blake wrote: > [adding-gnulib] I'm not subscribed, please (continue to) keep me in CC. > On 10/18/2012 06:50 AM, Peter Rosin wrote: >> Hi! >> >> I used to use a libtool git checkout from a platform that lacks >> git [MSY

Re: bug#9847: [PATCH 3/3] maint: use gnulib's gitlog-to-changelog instead of a ChangeLog file.

Gary V. Vaughan skrev 2011-10-31 16:36: > Hi Peter, > > On 31 Oct 2011, at 22:24, Peter Rosin wrote: >> Gary V. Vaughan skrev 2011-10-23 18:17: >>> We already have to enter all the ChangeLog relevant information into the git >>> commit log. Instead of worryi

Re: autoconf + automake support for MSVC

Den 2011-09-11 00:04 skrev Bruno Haible: > Peter Rosin wrote: >> The main benefits that I see are that you don't have to >> cross compile if you are in MSYS > > You have the wrong notion of "cross compile", if you think cross-compiling > means that $host !=

Re: autoconf + automake support for MSVC

Den 2011-09-10 02:22 skrev Bruno Haible: > Peter Rosin wrote: >> The platform name was discussed a few years back on the libtool lists (I >> think somewhere in the gigantic thread "[patch #6448] [MSVC 7/7] Add MSVC >> Support" from August 2008 approximately) [0],

Re: autoconf + automake support for MSVC

Den 2011-09-09 19:27 skrev Bruno Haible: > But since not all packages use the AM_PROG_CC_C_O macro (only the use of > source files in directories without a Makefile.in requires it), I would > better recommend to everyone to use CC="/path/to/compile cl -nologo" > from the beginning. But don't forge

Re: autoconf + automake support for MSVC

Den 2011-09-09 19:00 skrev Bruno Haible: > Peter Rosin wrote: >>> When configure.ac does not contain then AM_PROG_CC_C_O macro, >>> what do you do? Add it manually? ... >> >> In that case, as stated above, you can just use compile/ar-lib as you'd >> use

Re: autoconf + automake support for MSVC

Hi Stefano, Den 2011-09-03 09:41 skrev Stefano Lattarini: > On Saturday 03 September 2011, Peter Rosin wrote: >> >> [BIG SNIP] >> >> I don't think cccl is the future, I see it as the past. It's >> simply not needed when the needed bits are already in &#x

Re: autoconf + automake support for MSVC

Den 2011-09-03 03:47 skrev Bruno Haible: > Peter Rosin wrote: >> I didn't want to create yet another fork of cccl, and instead fixed >> the 'compile' script in Automake to handle the bits that must be >> handled by the build tools (and taught libtool to deal wi

Re: autoconf + automake support for MSVC

Den 2011-09-03 00:43 skrev Michael Goffioul: > On Fri, Sep 2, 2011 at 11:26 PM, Peter Rosin wrote: >> The web has a couple of different forked versions of cccl. What is >> the "upstream" for that script? There is ancient support for some >> version of cccl in libto

Re: autoconf + automake support for MSVC

Den 2011-09-02 23:11 skrev Bruno Haible: > Ralf Wildenhues wrote in > : Windows+MSVC. I know this is not a gnulib target. >>> >>> Yes. But it could become a gnulib target if the $CC wrapper script was >>> agreed >>> upon in G