All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Czarnowski, Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@linux.intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: Virtual Media repository request
Date: Mon, 19 Dec 2022 15:01:25 +0100	[thread overview]
Message-ID: <8a15e91f-a8a1-0a70-1006-d07dafdd7b34@linux.intel.com> (raw)
In-Reply-To: <4ab2d31e-4433-5987-c2ad-8f3d4ce50090@linux.intel.com>

On 23.12.2021 02:01, Czarnowski, Przemyslaw wrote:
> On 20.12.2021 13:54, Czarnowski, Przemyslaw wrote:
>>
>> I plan to start pushing changes here this week.
>>
> Replying to myself, but just pushed a series of first 4 patches to review.
> 
> It is just a skeleton (infrastructure to build main flows on) but wanted 
> to get the first reviews for initial changes (transition from old 
> content to the new one in particular).
> 

I would like to rise the request for new service of Virtual Media 
repository once again.

Recently I've made an attempt to push VM service patches once again 
after UT has been added. In the meantime, I've noticed that in order to 
make a graceful transition between old and new solution the final switch 
between the old and new code should be made at the moment when the last 
patch is accepted.

There are two main reason why I would like to recall the discussion.
First is the voice of the maintainer of the old service. Second - 
problems with linting and CI which wants to build and test both projects 
simultaneously.

Of course the decision does not belong to me. I just do not want mess 
with current CI to support this transitional state.

-- 
Best regards,
Przemyslaw Czarnowski


  reply	other threads:[~2022-12-19 14:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 15:50 Virtual Media repository request Hawrylewicz Czarnowski, Przemyslaw
2021-12-08 16:56 ` Patrick Williams
2021-12-09  8:56   ` Czarnowski, Przemyslaw
2021-12-09 10:41     ` i.kononenko
2021-12-13 16:10     ` Patrick Williams
2021-12-13 19:44       ` Czarnowski, Przemyslaw
2021-12-14  2:11       ` Jeremy Kerr
2021-12-15 19:26         ` Ed Tanous
2021-12-17  9:28           ` Czarnowski, Przemyslaw
2021-12-17  9:45             ` Jeremy Kerr
2021-12-20 12:54               ` Czarnowski, Przemyslaw
2021-12-23  1:01                 ` Czarnowski, Przemyslaw
2022-12-19 14:01                   ` Czarnowski, Przemyslaw [this message]
2022-12-19 17:43                     ` Ed Tanous
2023-01-03  5:36                     ` Jeremy Kerr
2021-12-11 21:13 ` Ed Tanous
2021-12-13 19:17   ` Czarnowski, Przemyslaw

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=8a15e91f-a8a1-0a70-1006-d07dafdd7b34@linux.intel.com \
    --to=przemyslaw.hawrylewicz.czarnowski@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    /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.