Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] Mailing list address
Date: Mon, 14 Sep 2015 11:56:33 +0100	[thread overview]
Message-ID: <55F6A7E1.4090500@imgtec.com> (raw)
In-Reply-To: <CAFOYHZCP=wKo23h1r9cDizkLQ-nNQW_o21+Otjm0V=NYJVvVRw@mail.gmail.com>

Dear Chris Packham,

On 09/14/2015 11:35 AM, Chris Packham wrote:
> Hi All,
> 
> Just noticed that README[1] mentions "buildroot at buildroot.org" but the
> buildroot website[2] says "buildroot at busybox.net". I just sent a patch
> to the former, assuming it must be an alias to the latter.

Yes, one is an alias of the other.

> I haven't
> seen a bounce but haven't seen it show up on the list yet.

I do see your patch on the list, and also in Patchwork:

http://patchwork.ozlabs.org/patch/517337/

> Is the address supposed to work as I've assumed or is it just a plain
> typo in README?

No, is not a typo. The buildroot.org address works and it's the one
everyone should use, IMHO.

> I'll re-send my patch to the other address in a couple of minutes.

Now we have your patch twice:

http://patchwork.ozlabs.org/patch/517346/

Can you please mark this one as "superseded" or "rejected" or "not
applicable" (I guess we need a "Duplicate" option) in Patchwork?

Regards,

Vincent.

> 
> --
> [1] - http://git.buildroot.net/buildroot/tree/README#n22
> [2] - http://lists.busybox.net/mailman/listinfo/buildroot
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

  reply	other threads:[~2015-09-14 10:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 10:35 [Buildroot] Mailing list address Chris Packham
2015-09-14 10:56 ` Vicente Olivert Riera [this message]
2015-09-14 10:58   ` Gustavo Zacarias
2015-09-14 22:40   ` Chris Packham
2015-09-14 12:41 ` Peter Korsgaard

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=55F6A7E1.4090500@imgtec.com \
    --to=vincent.riera@imgtec.com \
    --cc=buildroot@busybox.net \
    /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