From: "Darrick J. Wong" <djwong@kernel.org>
To: Nathan Scott <nathans@redhat.com>
Cc: Bastian Germann <bastiangermann@fishpost.de>,
Eric Sandeen <sandeen@sandeen.net>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH v2 0/6] debian: xfsprogs package clean-up
Date: Tue, 19 Jan 2021 13:42:52 -0800 [thread overview]
Message-ID: <20210119214252.GU3134581@magnolia> (raw)
In-Reply-To: <CAFMei7MbBu9zfoXfE9+mTo1TtMzov-DEPWj6KPfw7Aa_PMnU4g@mail.gmail.com>
On Wed, Jan 20, 2021 at 08:26:45AM +1100, Nathan Scott wrote:
> Hey all,
>
> On Wed, Jan 20, 2021 at 4:16 AM Bastian Germann
> <bastiangermann@fishpost.de> wrote:
> > [...]
> > Nathan uploaded most of the versions, so I guess he can upload.
> > The Debian package is "team maintained" though with this list address as
> > recorded maintainer.
> >
>
> You should have the necessary permissions to do uploads since
> yesterday Bastian - is that not the case?
>
> BTW Eric, not directly related but I think the -rc versions being
> added to the debian/changelog can lead to some confusion - I *think*
> dpkg finds that version suffix to be more recent than the actual
> release version string (seems odd, but that seemed to be the behaviour
> I observed recently). Could the release script(s) skip adding -rc
> versions to debian/changelog?
The release maintainer could also skip adding the ~rc tags to
debian/changelog since it's not like we're going to upload /that/ into
debian anyway. All of my internal builds add their own tag with dch, so
it wouldn't matter much to me.
(But let's see if Dave has opinions...)
--D
> cheers.
>
> --
> Nathan
>
next prev parent reply other threads:[~2021-01-19 21:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 18:37 [PATCH 0/6] debian: xfsprogs package clean-up Bastian Germann
2021-01-14 18:37 ` [PATCH 1/6] debian: cryptographically verify upstream tarball Bastian Germann
2021-01-14 18:37 ` [PATCH 2/6] debian: remove dependency on essential util-linux Bastian Germann
2021-01-14 20:48 ` Darrick J. Wong
2021-01-14 18:37 ` [PATCH 3/6] debian: remove "Priority: extra" Bastian Germann
2021-01-14 20:48 ` Darrick J. Wong
2021-01-14 18:37 ` [PATCH 4/6] debian: use Package-Type over its predecessor Bastian Germann
2021-01-14 20:51 ` Darrick J. Wong
2021-01-14 18:37 ` [PATCH 5/6] debian: add missing copyright info Bastian Germann
2021-01-14 18:37 ` [PATCH 6/6] debian: new changelog entry Bastian Germann
2021-01-14 20:56 ` Darrick J. Wong
2021-01-15 3:40 ` [PATCH 0/6] debian: xfsprogs package clean-up Nathan Scott
2021-01-15 4:14 ` Darrick J. Wong
2021-01-15 18:31 ` Eric Sandeen
2021-01-15 18:35 ` Eric Sandeen
2021-01-16 9:34 ` Bastian Germann
2021-01-18 1:37 ` Nathan Scott
2021-01-16 9:23 ` [PATCH v2 " Bastian Germann
2021-01-16 9:23 ` [PATCH v2 1/6] debian: cryptographically verify upstream tarball Bastian Germann
2021-01-16 9:23 ` [PATCH v2 2/6] debian: remove dependency on essential util-linux Bastian Germann
2021-01-16 9:23 ` [PATCH v2 3/6] debian: remove "Priority: extra" Bastian Germann
2021-01-16 9:23 ` [PATCH v2 4/6] debian: use Package-Type over its predecessor Bastian Germann
2021-01-16 9:23 ` [PATCH v2 5/6] debian: add missing copyright info Bastian Germann
2021-01-16 9:23 ` [PATCH v2 6/6] debian: new changelog entry Bastian Germann
2021-01-17 1:09 ` [PATCH v2 0/6] debian: xfsprogs package clean-up Eric Sandeen
2021-01-18 1:24 ` Nathan Scott
2021-01-18 21:33 ` Eric Sandeen
2021-01-19 15:02 ` Bastian Germann
2021-01-19 17:07 ` Eric Sandeen
2021-01-19 17:16 ` Bastian Germann
2021-01-19 21:26 ` Nathan Scott
2021-01-19 21:35 ` Bastian Germann
2021-01-19 21:42 ` Darrick J. Wong [this message]
2021-01-19 22:00 ` Eric Sandeen
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=20210119214252.GU3134581@magnolia \
--to=djwong@kernel.org \
--cc=bastiangermann@fishpost.de \
--cc=linux-xfs@vger.kernel.org \
--cc=nathans@redhat.com \
--cc=sandeen@sandeen.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;
as well as URLs for NNTP newsgroup(s).