From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 12.0.90 available for testing
Date: Fri, 08 Apr 2022 07:38:40 -0600 [thread overview]
Message-ID: <874k338zkv.fsf@tromey.com> (raw)
In-Reply-To: <Yk83W4ruSJQSCpVu@adacore.com> (Joel Brobecker via Gdb-patches's message of "Thu, 7 Apr 2022 12:11:23 -0700")
>> # The gnulib commit ID to use for the update.
>> -GNULIB_COMMIT_SHA1="776af40e09b476a41073131a90022572f448c189"
>> +GNULIB_COMMIT_SHA1="58c597d13bc57dce3e97ea97856573f2d68ccb8c"
>>
>> # The expected version number for the various auto tools we will
>> # use after the import.
Joel> Is it just code, or does this update also cause the imports to
Joel> somehow change? The import changes would be the only thing that
Joel> might raise red-flags for me. Other than that, I don't think
Joel> I'd need to see the diff, really. The import process being
Joel> automated IIRC, it's all mechanical, as you say.
I don't really know how to check this.
I re-ran update-gnulib.sh and it printed the appended module list.
Tom
Module list with included dependencies (indented):
absolute-header
accept
alloca
alloca-opt
arpa_inet
assure
at-internal
attribute
basename-lgpl
bind
btowc
builtin-expect
c99
canonicalize-lgpl
chdir
chdir-long
chown
clock-time
cloexec
close
closedir
connect
count-one-bits
ctype
d-ino
d-type
dirent
dirfd
dirname-lgpl
double-slash-root
dup
dup2
eloop-threshold
environ
errno
error
exitfail
extensions
extern-inline
fchdir
fcntl
fcntl-h
fd-hook
fd-safer-flag
fdopendir
ffs
filename
filenamecat-lgpl
flexmember
float
fnmatch
fnmatch-gnu
fnmatch-h
fpieee
fpucw
free-posix
frexp
frexpl
fstat
fstatat
gen-header
gendocs
getcwd
getcwd-lgpl
getdelim
getdtablesize
getline
getlogin_r
getprogname
getrandom
gettext-h
gettimeofday
gitlog-to-changelog
glob
glob-h
hard-locale
idx
include_next
inet_ntop
intprops
inttypes
inttypes-incomplete
isblank
isnand-nolibm
isnanl-nolibm
largefile
libc-config
limits-h
listen
localcharset
locale
lock
lstat
malloc-posix
malloca
math
mbrtowc
mbsinit
mbsrtowcs
mbtowc
memchr
memmem
memmem-simple
mempcpy
memrchr
minmax
mkdir
mkdtemp
mkostemp
msvc-inval
msvc-nothrow
multiarch
netdb
netinet_in
nocrash
open
openat
openat-die
openat-h
opendir
pathmax
pipe-posix
rawmemchr
readdir
readlink
realloc-posix
rename
rewinddir
rmdir
same-inode
save-cwd
scratch_buffer
select
setenv
setlocale-null
setsockopt
signal-h
snippet/_Noreturn
snippet/arg-nonnull
snippet/c++defs
snippet/warn-on-use
socket
socketlib
sockets
socklen
ssize_t
stat
stat-time
std-gnu11
stdalign
stdbool
stddef
stdint
stdio
stdlib
strchrnul
strdup-posix
streq
strerror
strerror-override
strerror_r-posix
string
strings
strnlen
strnlen1
strstr
strstr-simple
strtok_r
sys_random
sys_select
sys_socket
sys_stat
sys_time
sys_types
sys_uio
sys_wait
tempname
threadlib
time
time_r
unistd
unistd-safer
unsetenv
update-copyright
vararrays
verify
wchar
wctype-h
windows-mutex
windows-once
windows-recmutex
windows-rwlock
wmemchr
wmempcpy
xalloc-oversized
next prev parent reply other threads:[~2022-04-08 13:38 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 5:58 Joel Brobecker
2022-03-26 15:26 ` Eli Zaretskii
2022-03-26 15:53 ` Joel Brobecker
2022-03-26 16:15 ` Eli Zaretskii
2022-04-07 16:08 ` Tom Tromey
2022-04-07 16:12 ` Eli Zaretskii
2022-04-07 18:00 ` Joel Brobecker
2022-04-07 18:04 ` Simon Marchi
2022-04-07 19:02 ` Tom Tromey
2022-04-07 19:11 ` Joel Brobecker
2022-04-08 13:38 ` Tom Tromey [this message]
2022-04-08 14:33 ` Pedro Alves
2022-04-18 15:26 ` Tom Tromey
2022-04-18 16:13 ` Tom Tromey
2022-04-07 18:30 ` Tom Tromey
2022-04-08 6:58 ` Eli Zaretskii
2022-04-18 19:28 ` Tom Tromey
2022-03-26 17:59 ` Eli Zaretskii
2022-03-26 18:34 ` Eli Zaretskii
2022-03-26 18:51 ` Eli Zaretskii
2022-03-27 6:27 ` Eli Zaretskii
2022-03-31 6:23 ` Eli Zaretskii
2022-03-31 9:48 ` Pedro Alves
2022-03-31 11:55 ` Eli Zaretskii
2022-04-01 10:12 ` Andrew Burgess
2022-04-01 11:18 ` Eli Zaretskii
2022-04-01 11:25 ` Eli Zaretskii
2022-04-01 15:21 ` Andrew Burgess
2022-04-01 16:18 ` Eli Zaretskii
2022-04-03 13:02 ` Hannes Domani
2022-04-03 13:34 ` Eli Zaretskii
2022-04-03 14:03 ` Joel Brobecker
2022-04-03 15:26 ` Hannes Domani
2022-04-03 15:38 ` Eli Zaretskii
2022-04-07 11:09 ` Eli Zaretskii
2022-04-07 18:03 ` Joel Brobecker
2022-04-10 19:06 ` Joel Brobecker
2022-04-11 11:42 ` Eli Zaretskii
2022-04-17 17:28 ` Joel Brobecker
2022-04-19 16:12 ` Andrew Burgess
2022-04-19 16:16 ` Eli Zaretskii
2022-04-20 13:26 ` Andrew Burgess
2022-04-20 17:11 ` Joel Brobecker
2022-04-20 17:30 ` Eli Zaretskii
2022-04-24 15:56 ` Joel Brobecker
2022-04-25 8:48 ` Andrew Burgess
2022-04-07 18:28 ` Tom Tromey
2022-04-07 19:22 ` Pedro Alves
2022-04-08 4:04 ` Eli Zaretskii
2022-04-01 12:36 ` Joel Brobecker
2022-04-01 12:50 ` Eli Zaretskii
2022-04-01 14:12 ` Joel Brobecker
2022-04-01 14:27 ` Eli Zaretskii
2022-04-01 14:31 ` Joel Brobecker
2022-04-08 14:44 ` Pedro Alves
2022-04-08 20:05 ` Eli Zaretskii
2022-03-27 9:55 ` Eli Zaretskii
2022-03-27 1:55 ` Simon Marchi
2022-03-27 5:20 ` Eli Zaretskii
2022-04-07 16:13 ` Tom Tromey
2022-04-07 16:39 ` Eli Zaretskii
2022-03-31 6:21 ` Eli Zaretskii
2022-03-31 9:44 ` Pedro Alves
2022-03-31 11:58 ` Eli Zaretskii
2022-03-31 12:05 ` Pedro Alves
2022-03-31 14:00 ` Eli Zaretskii
2022-04-12 14:01 ` Luis Machado
2022-04-12 17:57 ` Joel Brobecker
2022-04-13 7:36 ` Luis Machado
2022-04-13 12:19 ` Luis Machado
2022-04-13 16:20 ` Jose E. Marchesi
2022-04-17 17:33 ` Joel Brobecker
2022-04-18 1:48 ` Alan Modra
2022-04-26 13:54 ` Luis Machado
2022-04-26 14:56 ` Joel Brobecker
2022-04-26 15:15 ` Luis Machado
2022-04-20 17:33 ` Pedro Alves
2022-04-20 17:52 ` 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=874k338zkv.fsf@tromey.com \
--to=tom@tromey.com \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).