From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/x11r7/xdriver_xf86-video-vmware: fix compilation without udev
Date: Fri, 03 Mar 2017 20:32:27 +0100 [thread overview]
Message-ID: <87tw7af96c.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170302113244.kjszgkgdmcn3xtmu@tarshish> (Baruch Siach's message of "Thu, 2 Mar 2017 13:32:44 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Hi Peter,
> On Thu, Mar 02, 2017 at 08:12:50AM +0100, Peter Korsgaard wrote:
>> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>> > Applied to master, thanks. Peter, this one could go to the LTS branch.
>>
>> Thanks, applied to 2017.02.x.
> Is there a reason why 2017.02.x branch commits are not posted to the list?
> Commits to the 2016.11.x branch used to appear on the list.
They are (I see them at least). I think the issue is just that the
send-mail script has a minor bug when a new branch is pushed. In that
case it sends a small mail saying 'new branch created', and forgets to
send a notification mail for the individual commits added in that push.
I did my initial push with 3 commits, that is why no notification is
sent for those 3 commits.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-03-03 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 14:32 [Buildroot] [PATCH 1/1] package/x11r7/xdriver_xf86-video-vmware: fix compilation without udev Bernd Kuhls
2017-03-01 22:40 ` Thomas Petazzoni
2017-03-02 7:12 ` Peter Korsgaard
2017-03-02 11:32 ` Baruch Siach
2017-03-03 19:32 ` Peter Korsgaard [this message]
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=87tw7af96c.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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