From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <gfarnum@redhat.com>
Cc: Gregory Meno <gmeno@redhat.com>, Alfredo Deza <adeza@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Building packages from a SHA instead of the tip of a branch
Date: Fri, 26 Feb 2016 01:33:17 +0700 [thread overview]
Message-ID: <56CF48ED.2020104@dachary.org> (raw)
In-Reply-To: <CAJ4mKGbR-PnAztnEYzPjjyOS9gbh5EHBrx8Y=iZQTTugf=TS_A@mail.gmail.com>
Hi Greg,
On 26/02/2016 00:37, Gregory Farnum wrote:
> On Thu, Feb 25, 2016 at 4:28 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Gregory and Alfredo,
>>
>> The system in place to build packages uses the tip of the stable branch, which has been a recurring problem over the past years. It would make a lot of sense to use a specific SHA1 instead of "whatever is at the tip of the stable branch at the moment".
>>
>> Is there already an issue in tracker.ceph.com for this ? If not, in which tracker do you suggest I file this feature request ?
>
> It might be easier to build from a tag or to push a specifically-named
> branch (infernalis-release-2016-02-25) as well. Just to think around
> the problem. ;)
IIRC taging was not an option because people have scripts watching the tags (it's a distant memory though, maybe it does not matter anymore ?). I like the idea of having an infernalis-release-2016-02-25 branch. Unless the scripts are somehow sensitive to the branch name ?
Cheers
> -Greg
>
--
Loïc Dachary, Artisan Logiciel Libre
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-02-25 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 12:28 Building packages from a SHA instead of the tip of a branch Loic Dachary
2016-02-25 17:37 ` Gregory Farnum
2016-02-25 18:33 ` Loic Dachary [this message]
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=56CF48ED.2020104@dachary.org \
--to=loic@dachary.org \
--cc=adeza@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gfarnum@redhat.com \
--cc=gmeno@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 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.