From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [commit 1/3] Import gnulib's update-copyright script
Date: Wed, 18 Apr 2012 15:12:00 -0000 [thread overview]
Message-ID: <87d375qdo3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120418145225.GC2852@adacore.com> (Joel Brobecker's message of "Wed, 18 Apr 2012 07:52:25 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> Sure. Since there does not appear to be gnulib releases, I was
Joel> under the impression that we'd always go with the current head,
Joel> somehow. Having the hash in the script is a good idea, makes
Joel> things completely reproduceable...
Yes, I think most gnulib users just update it using gnulib master.
Last time we discussed this, Mark K. said that our approach was to
update it based on need.
Recording the revision somewhere obvious (not ChangeLog perhaps but
maybe a file in the "wrapping" directory, whatever it is called?) seems
ok to me.
Tom
next prev parent reply other threads:[~2012-04-18 15:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 8:20 New procedure for updating copyright years Joel Brobecker
2012-01-04 8:20 ` [commit 2/3] use gnulib's update-copyright script to update " Joel Brobecker
2012-01-04 8:20 ` [RFA/doco 3/3] Document new procedure for updating " Joel Brobecker
2012-01-04 18:24 ` Eli Zaretskii
2012-01-05 3:34 ` Joel Brobecker
2012-01-05 5:44 ` Eli Zaretskii
2012-01-05 9:42 ` Joel Brobecker
2012-01-04 8:20 ` [commit 1/3] Import gnulib's update-copyright script Joel Brobecker
2012-04-18 12:41 ` Pedro Alves
2012-04-18 14:37 ` Joel Brobecker
2012-04-18 14:52 ` Pedro Alves
2012-04-18 14:54 ` Joel Brobecker
2012-04-18 15:10 ` Pedro Alves
2012-04-18 15:12 ` Tom Tromey [this message]
2012-04-18 20:52 ` Import gnulib's update-copyright whole module Pedro Alves
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=87d375qdo3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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