From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gnuplot: bump to version 5.2.8
Date: Thu, 27 Feb 2020 10:15:25 +0100 [thread overview]
Message-ID: <20200227101525.6e7cdf21@windsurf> (raw)
In-Reply-To: <434318d67af84622b1a9200b63e18220@go-sys.de>
Hello Michael,
Please keep the Buildroot mailing list in Cc by using "reply all" when
replying to Buildroot messages. Thanks!
On Thu, 27 Feb 2020 08:58:35 +0000
Michael Fischer <mf@go-sys.de> wrote:
> >Thanks for your contribution! If you're using gnuplot in Buildroot, would you be willing to be listed as a developer for this package in our DEVELOPERS file? This would help us maintain this package on the long run.
>
> I use gnuplot and buildroot in our new software project so I'm willing to help as a developer if I can.
Great! Could you send a patch adding you to the DEVELOPERS file in
Buildroot ?
> >Why did you add some - signs in front the description and Signed-off-by lines? I dropped these, so that the patch description looks normal.
>
> Hmm,
> It's a copy of the entry from Vincent. I'm new in create git patches and so I thought it's normal.
You had added - signs in front of each line of the description, which
were not correct.
Anyway, I fixed that up, no worries.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-27 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 9:06 [Buildroot] [PATCH] package/gnuplot: bump to version 5.2.8 Michael Fischer
2020-02-26 21:45 ` Thomas Petazzoni
[not found] ` <434318d67af84622b1a9200b63e18220@go-sys.de>
2020-02-27 9:15 ` Thomas Petazzoni [this message]
2020-02-27 12:10 ` Michael Fischer
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=20200227101525.6e7cdf21@windsurf \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.