public inbox for
 help / color / mirror / Atom feed
From: Chris Packham <>
To: Geert Stappers <>,
	""	<>
Subject: Re: Regarding: Bug#721430: crosstool-ng, startpoint for further effort
Date: Sun, 28 May 2017 21:25:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 27/05/17 22:03, Geert Stappers wrote:
> On Wed, May 24, 2017 at 03:42:45PM +0200, Geert Stappers wrote:
>> Hello Chris,
> Hello again
>> On Mon, May 22, 2017 at 09:11:14PM +0000, Chris Packham wrote:
>>> On 23/05/17 09:05, Geert Stappers wrote:
>>>> On Sun, May 21, 2017 at 09:10:03PM +0000, Chris Packham wrote:
>>>>> I think I need to at least update my PR against the latest released
>>>>> version
>>>> I have a git clone of
>>>> found the patch for the PR.
>>>> I'll join it with my work from yesterday.
>>>> And we have to find a way how we join effort.
>>> OK let me know if you need any help. I think the patch should rebase
>>> cleanly against master.
>> We both did change debian/control and debian/changelog
>> there would have been an git merge conflict.
>> I have merged our work.  The result is attached.
>> Looking forward for your feedback.
> Thing that interrests me most is
> if you want to be the maintainer of crosstools-ng

It would make sense for Alexy (@stilor) to be the maintainer of the 
debian packaging but I don't mind taking it off his plate if he's too 
busy. The packaging doesn't necessarily have to have the same 
maintainership as crosstool-ng itself.

> Find attached another debian tarball for ct-ng.
> Change is addition of 'wget' and 'curl' as build dependencies.

I haven't had a chance to look at your changes yet but adding wget and 
curl seems sane. The only thing is that if something is in the 
build-essentials package then it's not generally listed as an explicit 

> Also as "retransmit" because I don't know if recieved the previous one.

Yes It came through, just trying to find some time to look at it.


I'll incorporate Geert's changes an update PR352. Still looking for an 
actual Debian developer help get this into unstable/testing/whatever.

       reply	other threads:[~2017-05-28 21:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
     [not found]       ` <>
     [not found]         ` <>
     [not found]           ` <>
2017-05-28 21:25             ` Chris Packham [this message]
2017-06-02 17:54               ` crosstool-ng mailinglist and Debian developer Geert Stappers
2017-06-05 23:49                 ` Chris Packham
2017-06-06 22:00                   ` Geert Stappers

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).