From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Willian Rampazzo" <willianr@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>, "Bin Meng" <bmeng.cn@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 0/1] gitlab-ci: Only push docker images to mainstream registry from /master
Date: Wed, 27 Oct 2021 13:34:09 +0100 [thread overview]
Message-ID: <YXlHQXWoLpvT7ukX@redhat.com> (raw)
In-Reply-To: <20211027122658.ieazn3sykshtlth4@sirius.home.kraxel.org>
On Wed, Oct 27, 2021 at 02:26:58PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > Notably the latter is more restrictive that git branch names. We could
> > assume users always have "sensible" branch names that are less than
> > 128 chars and only alpha-num characters plus dash/underscore. This
> > would be fine for my personal branch naming, but I wonder if anyone
> > uses wierd branch names that would violate docker tag name rules ?
>
> /me uses slashes in branch names, i.e.
>
> queue/$topic for patch queues
> $hostname/$subject for my development branches.
Ok, good to know. So that example clearly rules out use of git branch
names as docker tags.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-10-27 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 14:55 [PATCH 0/1] gitlab-ci: Only push docker images to mainstream registry from /master Philippe Mathieu-Daudé
2021-10-26 14:55 ` [PATCH 1/1] gitlab-ci: Only push docker images to registry from /master branch Philippe Mathieu-Daudé
2021-10-26 21:04 ` Willian Rampazzo
2021-10-27 6:01 ` Thomas Huth
2021-10-27 8:44 ` Daniel P. Berrangé
2021-10-27 11:35 ` Gerd Hoffmann
2021-10-27 11:46 ` Daniel P. Berrangé
2021-10-27 8:50 ` Philippe Mathieu-Daudé
2021-10-27 11:44 ` [PATCH 0/1] gitlab-ci: Only push docker images to mainstream registry from /master Daniel P. Berrangé
2021-10-27 12:26 ` Gerd Hoffmann
2021-10-27 12:34 ` Daniel P. Berrangé [this message]
2021-10-27 13:02 ` Philippe Mathieu-Daudé
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=YXlHQXWoLpvT7ukX@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bmeng.cn@gmail.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=michael.roth@amd.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).