Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dmitry Samersoff <dms@samersoff.net>
To: amodra@gmail.com
Cc: gdb@sourceware.org
Subject: Background of daily update changeset?
Date: Sat, 28 Dec 2013 07:35:00 -0000	[thread overview]
Message-ID: <52BE7F20.8010709@samersoff.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Everyone,

What is the goal of daily update of BFD_VERSION_DATE?

Could you give me more background of it.

e.g.:

date:        Sat May 01 00:00:05 2010 +0000
summary:     daily update


diff -r 0be0bbf11bc2 -r a395e574294e bfd/version.h
- --- a/bfd/version.h     Sat May 01 00:00:03 2010 +0000
+++ b/bfd/version.h     Sat May 01 00:00:05 2010 +0000
@@ -1,4 +1,4 @@
- -#define BFD_VERSION_DATE 20100430
+#define BFD_VERSION_DATE 20100501
 #define BFD_VERSION @bfd_version@
 #define BFD_VERSION_STRING  @bfd_version_package@ @bfd_version_string@
 #define REPORT_BUGS_TO @report_bugs_to@

- -Dmitry

- -- 
Dmitry Samersoff
Saint Petersburg, Russia, http://devnull.samersoff.net
* There will come soft rains  ...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSvn8gAAoJEHEy08c4gIABsKYIAIgQeQGDDi8roqkxVBYSImEG
01wvQ3A4MMPnF4e3jaHHD64AX3Uqc+CAiDX/eVTVxngbdVe00YW2rDAFl2bDhnM4
EgBFLmb+dYrplal9N1HQWzviKvDtUkGrjdHQEh6P3358hq0TzFddZIZOrMTqPgNh
skIRJrWqYXsBwtrYuidQ8LfwSTfj2DaOW9vK4Yc1UsMfuZZXdUSw/ugypwd8BSuC
MyhW+d8CXy4Asc0GEuuHB6NQ5ZQRckpyiu0HuD3V3Qs3n9kCFXPLEx7+R9c2zGrf
TpBW8M4LnL9u1Gh/dFx8EJw8FwmFsECqt3Z+ooHwuSkDC1pzSAk5/O9hBEWlGMM=
=Mf9d
-----END PGP SIGNATURE-----


             reply	other threads:[~2013-12-28  7:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28  7:35 Dmitry Samersoff [this message]
2014-01-02 18:54 ` Paweł Sikora
2014-01-13 17:28 ` Tom Tromey
2014-01-14  0:56   ` Alan Modra
2014-01-14 14:36     ` Tom Tromey

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=52BE7F20.8010709@samersoff.net \
    --to=dms@samersoff.net \
    --cc=amodra@gmail.com \
    --cc=gdb@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