public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Kubacki <wmark@hurrikane.de>
To: gentoo-portage-dev@lists.gentoo.org
Cc: W-Mark Kubacki <wmark@hurrikane.de>
Subject: [gentoo-portage-dev] [PATCH 0/3] Implement a more verbose User-Agent HTTP-header
Date: Wed, 14 Aug 2013 22:10:37 +0200	[thread overview]
Message-ID: <1376511040-15874-1-git-send-email-wmark@hurrikane.de> (raw)

From: W-Mark Kubacki <wmark@hurrikane.de>

Before this patch series Portage identified itself as
> Gentoo Portage
Now it will be the output of ```emerge --version```, i.e.:
> Gentoo Portage 2.1.13.7 (default/linux/amd64/13.0, gcc-4.6.2, 
> glibc-2.18, 3.9.0-rc8-mark-signed+ x86_64, 
> Intel(R) Core(TM) i7-3770T CPU @ 2.50GHz)

That longer string makes debugging easier and helps deciding
when to deploy changes on the Gentoo binhost's side.

W-Mark Kubacki (3):
  Send exact version with User-Agent HTTP-header
  Send output of ```emerge --version``` as User-Agent HTTP-header
  Add CPU model name to output of getportageversion as fifth element

 pym/_emerge/actions.py       | 4 +++-
 pym/portage/dbapi/bintree.py | 8 +++++++-
 pym/portage/util/_urlopen.py | 5 +++--
 3 files changed, 13 insertions(+), 4 deletions(-)

-- 
1.8.3.2



             reply	other threads:[~2013-08-14 20:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 20:10 Mark Kubacki [this message]
2013-08-14 20:10 ` [gentoo-portage-dev] [PATCH 1/3] Send exact version with User-Agent HTTP-header Mark Kubacki
2013-08-14 20:10 ` [gentoo-portage-dev] [PATCH 2/3] Send output of ```emerge --version``` as " Mark Kubacki
2013-08-15  6:25   ` Zac Medico
2013-08-14 20:10 ` [gentoo-portage-dev] [PATCH 3/3] Add CPU model name to output of getportageversion as fifth element Mark Kubacki
2013-08-14 20:27   ` [gentoo-portage-dev] " Mark Kubacki
2013-08-15  8:00   ` [gentoo-portage-dev] " Fabian Groffen
2013-08-24 22:39     ` Mike Frysinger
2013-08-15 10:58   ` Alexander Berntsen
2013-08-24 22:38     ` Mike Frysinger

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=1376511040-15874-1-git-send-email-wmark@hurrikane.de \
    --to=wmark@hurrikane.de \
    --cc=gentoo-portage-dev@lists.gentoo.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