From: Till Kamppeter <till.kamppeter@gmail.com>
To: Rudra Pratap Singh <rudransh.iitm@gmail.com>
Cc: Michael Sweet <msweet@msweet.org>,
OpenPrinting <printing-architecture@lists.linux.dev>,
Cristovao Cordeiro <cristovao.cordeiro@canonical.com>,
Soumyadeep Ghosh <soumyadeepghosh2004@zohomail.in>
Subject: Re: Merge repositories for CUPS Snap and CUPS OCI/Docker Container into the CUPS repo itself
Date: Sun, 22 Dec 2024 16:40:57 +0100 [thread overview]
Message-ID: <7fa0204d-0804-4d7a-bb10-ff228dea2e67@gmail.com> (raw)
In-Reply-To: <CADmOQadkw-BY2vNqQtJDqi7TqGpHErVM29rkPfGAajiFVhGUiw@mail.gmail.com>
On 12/22/24 16:37, Rudra Pratap Singh wrote:
> It would be easier to pass the path of the README (or any Markdown file) where
> we want to list the parts, directly in the workflow itself.
OK, yes, you are right. We have the workflow in each repo with automation ...
Let us do it this way.
Till
next prev parent reply other threads:[~2024-12-22 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 23:55 Merge repositories for CUPS Snap and CUPS OCI/Docker Container into the CUPS repo itself Till Kamppeter
2024-12-21 21:06 ` Michael Sweet
2024-12-21 21:55 ` Till Kamppeter
2024-12-21 23:33 ` Michael Sweet
[not found] ` <CADmOQacnfVS5VR+dpudVt2NxgV_HG+K0in0mm-h5Hwe0nfF0cQ@mail.gmail.com>
2024-12-22 13:43 ` Michael Sweet
2024-12-22 14:03 ` Till Kamppeter
2024-12-22 14:44 ` Michael Sweet
2024-12-22 15:28 ` Till Kamppeter
[not found] ` <CADmOQafms3c=7FAzeX9cbvnPOYDcf9Xxe9QyKUjYEYTgJq3AJw@mail.gmail.com>
2024-12-22 15:33 ` Till Kamppeter
[not found] ` <CADmOQadkw-BY2vNqQtJDqi7TqGpHErVM29rkPfGAajiFVhGUiw@mail.gmail.com>
2024-12-22 15:40 ` Till Kamppeter [this message]
[not found] ` <CADmOQae0YNffRYsMZLLcwMY2GxFpThyfaq5Hm0rw=ke0pkuvZw@mail.gmail.com>
[not found] ` <CADmOQaf4hsBwrz-qkW_o8SZnfP1faD9ma4+T1FyA_GUYRgKhuQ@mail.gmail.com>
2025-01-13 17:55 ` Michael Sweet
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=7fa0204d-0804-4d7a-bb10-ff228dea2e67@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=cristovao.cordeiro@canonical.com \
--cc=msweet@msweet.org \
--cc=printing-architecture@lists.linux.dev \
--cc=rudransh.iitm@gmail.com \
--cc=soumyadeepghosh2004@zohomail.in \
/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.