From: Geert Stappers <stappers@stappers.nl>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Cross GCC <crossgcc@sourceware.org>,
crosstools-ng in debian <721430@bugs.debian.org>
Subject: Re: crosstool-ng Debian Maintainer
Date: Thu, 08 Jun 2017 21:27:00 -0000 [thread overview]
Message-ID: <20170607061229.GK26118@gpm.stappers.nl> (raw)
In-Reply-To: <7cfde562b8b941debe12b26e67878d97@svr-chch-ex1.atlnz.lc>
On Tue, Jun 06, 2017 at 10:00:35PM +0000, Chris Packham wrote:
> On 07/06/17 04:20, Geert Stappers wrote:
> > On Mon, Jun 05, 2017 at 11:49:10PM +0000, Chris Packham wrote:
> > > Where to next.
> >
> > Consider this
> >
> > --- a/debian/changelog
> > +++ b/debian/changelog
> > @@ -2,7 +2,7 @@ crosstool-ng (1.23.0-1) unstable; urgency=low
> > - -- Multiple Candidates <open@example.com> Wed, 24 May 2017 13:47:31 +0200
> > + -- Chris Packham <Chris.Packham@alliedtelesis.co.nz> Tue, 06 Jun 2017 17:58:00 +0200
> > --- a/debian/control
> > +++ b/debian/control
> > @@ -1,7 +1,8 @@
> > -Maintainer: Multiple Candidates <open@example.com>
> > +Maintainer: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
> > +Uploaders: Geert Stappers <stappers@debian.org>
> >
>
> I will raise a new PR for that.
Wait with that. If it is allready created, also fine.
> Do you have a handle on github so that I can tag you in the comments to review?
>
Groeten
Geert Stappers
--
Leven en laten leven
next prev parent reply other threads:[~2017-06-07 6:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 7:31 crosstool-ng mailinglist and Debian developer Chris Packham
2017-06-08 21:27 ` Geert Stappers [this message]
[not found] ` <20170608211216.GL26118@gpm.stappers.nl>
2017-06-08 22:06 ` Bug#721430: crosstool-ng Debian upload pending Chris Packham
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=20170607061229.GK26118@gpm.stappers.nl \
--to=stappers@stappers.nl \
--cc=721430@bugs.debian.org \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=crossgcc@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).