From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: archer@sourceware.org
Subject: Brief stats for Fedora *.patch merge
Date: Mon, 01 Nov 2010 17:36:00 -0000 [thread overview]
Message-ID: <20101101173626.GA11039@host0.dyn.jankratochvil.net> (raw)
Hi,
FYI some brief stats on the Fedora trunk merge status. One should rebase it to
7.2.50.* first for F15=7.3 to rebase the patches to HEAD before trying to push
them to avoid rebasing them possibly twice.
fedpkg clone -b f14 -a gdb; cd gdb # fedpkg sources
grep '^#=.' gdb.spec |sed 's/:.*//'|sort|uniq -c|sort -nr
40 #=push
35 #=fedoratest
24 #=drop
15 #=push+work
14 #=maybepush
7 #=ia64
4 #=fedoratest+ppc
2 #=maybepush+work
2 #=maybepush+ppc
2 #=fedoratest+work
1 #=fedora
1 #=drop+work
more general summary:
grep '^#=.' gdb.spec |sed 's/:.*//'|sed 's/+.*//'|sort|uniq -c|sort -nr
55 #=push
41 #=fedoratest
25 #=drop
18 #=maybepush
7 #=ia64
1 #=fedora
cat $(egrep -A1 '^#=(maybe)?push' gdb.spec|sed -n 's/^Patch.*: //p')|wc
11018 49121 379064
cat $(egrep -A1 '^#=(maybe)?push' gdb.spec|sed -n 's/^Patch.*: //p')|grep ^+|wc
6288 29704 209858
#push=Should be pushed upstream.
#maybepush=Should be pushed upstream unless it got obsoleted there.
#fedora=Should stay as a Fedora patch.
#ia64=Drop after RHEL-5 rebases and rebuilds are no longer meaningful.
#fedoratest=Keep it in Fedora only as a regression test safety.
#+ppc=Specific for ppc32/ppc64/ppc*
#+work=Requires some nontrivial work.
drop vs. push vs. maybepush and whether +work are only a rough guess of mine.
Regards,
Jan
next reply other threads:[~2010-11-01 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 17:36 Jan Kratochvil [this message]
2010-11-01 21:00 ` Tom Tromey
2010-11-01 21:14 ` Jan Kratochvil
2010-11-18 4:42 ` Fedora 15 patchset rebased to FSF GDB HEAD [Re: Brief stats for Fedora *.patch merge] Jan Kratochvil
2010-11-18 15:58 ` Phil Muldoon
2010-11-19 21:05 ` 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=20101101173626.GA11039@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=archer@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).