DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Boyer <aboyer@pensando.io>,
	David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Aaron Conole <aconole@redhat.com>,
	Michael Santana <maicolgabriel@hotmail.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <arybchenko@solarflare.com>
Subject: Re: [dpdk-dev] [PATCH] ci: fix package installation in GitHub Actions
Date: Mon, 4 Jan 2021 12:26:04 +0000
Message-ID: <7cc0ce51-5d88-9824-382b-175902016b4f@intel.com> (raw)
In-Reply-To: <1430424D-F3A9-4AB8-93F7-F1A38A7C33E6@pensando.io>

On 12/30/2020 6:00 PM, Andrew Boyer wrote:
> Hello David,
> I’m hitting this issue on the next/dpdk-next-net branch. Is there a way to pull the patch into all of the next-* branches so that others don’t hit it too?
> 

next-net rebased on the main repo to include the commit, fyi.

For the next trees, you can find their maintainers in the MAINTAINERS file.

> For now I've pulled it into my own branch.
> 
> This Actions thing is cool. It’s a huge timesaver.
> 
> Thank you,
> Andrew
> 
>> On Dec 21, 2020, at 12:27 PM, David Marchand <david.marchand@redhat.com> wrote:
>>
>> On Sat, Dec 19, 2020 at 9:26 AM David Marchand
>> <david.marchand@redhat.com> wrote:
>>>
>>> APT cache must be updated to avoid trying to install an unavailable
>>> version of a package.
>>>
>>> Fixes: 87009585e293 ("ci: hook to GitHub Actions")
>>>
>>> Signed-off-by: David Marchand <david.marchand@redhat.com>
>>
>> Applied.
>>
>>
>> -- 
>> David Marchand
>>
> 


  reply	other threads:[~2021-01-04 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19  8:26 David Marchand
2020-12-21 17:27 ` David Marchand
2020-12-30 18:00   ` Andrew Boyer
2021-01-04 12:26     ` Ferruh Yigit [this message]
2021-01-05  8:49     ` David Marchand

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=7cc0ce51-5d88-9824-382b-175902016b4f@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=aboyer@pensando.io \
    --cc=aconole@redhat.com \
    --cc=arybchenko@solarflare.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maicolgabriel@hotmail.com \
    --cc=thomas@monjalon.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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git