Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA] script to update our gnulib-import (take 2)
Date: Wed, 24 Oct 2012 21:10:00 -0000	[thread overview]
Message-ID: <20121024210951.GI3523@adacore.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Hello,

This is an updated version of the script I proposed a few months ago:
http://www.sourceware.org/ml/gdb-patches/2011-12/msg00337.html

At the time, we held off on it because gnulib's bootstrap was
supposed to do the same thing. It's been 10+ months since that
suggestion was made, so I think we should go ahead with this script.

Independently of bootstrap, what this script brings is a verification
that the right versions of the auto-tools are being used. This avoid
unwanted changes due to differing versions. It also allows us to store
the gnulib SHA1 used for the import, rather than having to fish
it out from somewhere in a ChangeLog file.

If someone ever gets to using gnulib's bootstrap, then great - I think
it can easily be folded into this script. In the meantime, it helps,
because I no longer have to figure how to regenerate the configury
and the makefiles...

gdb/ChangeLog:

        * gnulib/update-gnulib.sh: New script.

Script tested by running it, and verifying that it does not introduce
any change.

OK to commit?

Thanks,
-- 
Joel

[-- Attachment #2: update-gnulib.sh --]
[-- Type: application/x-sh, Size: 4002 bytes --]

             reply	other threads:[~2012-10-24 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 21:10 Joel Brobecker [this message]
2012-10-30 20:31 ` Tom Tromey
2012-11-05 23:10   ` Joel Brobecker
2012-11-05 23:38     ` Joel Brobecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121024210951.GI3523@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox