From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit 1/3] Import gnulib's update-copyright script
Date: Wed, 18 Apr 2012 14:54:00 -0000 [thread overview]
Message-ID: <20120418145225.GC2852@adacore.com> (raw)
In-Reply-To: <4F8ED35E.1040208@redhat.com>
> I don't see how that scripts would have prevented the selective
> check-in. :-)
Perhaps not, but what I would have done was doing an update first,
check that in, and then add the new module. WDYT?
> It may help by keeping the git version in some script variable, that
> the script checks, instead of having to fetch the version from the
> ChangeLog? The new gnulib/ parent directory seems like a good place
> for this stuff.
Sure. Since there does not appear to be gnulib releases, I was
under the impression that we'd always go with the current head,
somehow. Having the hash in the script is a good idea, makes
things completely reproduceable...
--
Joel
next prev parent reply other threads:[~2012-04-18 14:52 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 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 [this message]
2012-04-18 15:10 ` Pedro Alves
2012-04-18 15:12 ` Tom Tromey
2012-04-18 20:52 ` Import gnulib's update-copyright whole module Pedro Alves
2012-01-04 8:20 ` [commit 2/3] use gnulib's update-copyright script to update copyright years 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
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=20120418145225.GC2852@adacore.com \
--to=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