From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-81543-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id B6F5F139694
for <garchives@archives.gentoo.org>; Tue, 25 Jul 2017 22:27:03 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 901E7E0E98;
Tue, 25 Jul 2017 22:26:56 +0000 (UTC)
Received: from mail-yw0-x243.google.com (mail-yw0-x243.google.com [IPv6:2607:f8b0:4002:c05::243])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 3C883E0D90
for <gentoo-dev@lists.gentoo.org>; Tue, 25 Jul 2017 22:26:55 +0000 (UTC)
Received: by mail-yw0-x243.google.com with SMTP id p68so3653258ywg.5
for <gentoo-dev@lists.gentoo.org>; Tue, 25 Jul 2017 15:26:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=mime-version:sender:in-reply-to:references:from:date:message-id
:subject:to:content-transfer-encoding;
bh=b+PDe0+TYmDma+hvy1IBajMnv1YFDz7Zy4CpjgIhknE=;
b=ac520jail+EqaGS4To2SkSoYDr+DN0M4L0qvq677gu9bTZwflAG913NfOqWwBBwfKS
AScrfh3bDdodcYw1sHapzzyxw7ZqAcEvRCaIwSxcf+WVd397dJhTv6QcQzrJBNv8oy8Y
DPBbuxP8ahAdB4Yk8Rk4FShok+JDWFKUPAOTFwm/2DoP2HaLwRWaCfLLqEU93Bp0v/RC
YOcea4GytmDVECmx13n+psD9w6Yd37o7vxuBkJ86UR5DwFGJ9yQlB0D9YNtCK3zAT0YZ
3V/CoKmxoxNsRSbFk44FbQoWdT865IOPUHpumucQSA7g9Y8dKyyM7sFBo3MOgoGW0moV
pU+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:to:content-transfer-encoding;
bh=b+PDe0+TYmDma+hvy1IBajMnv1YFDz7Zy4CpjgIhknE=;
b=nTSVotSSQu74W3HN+pIJEXlY3JatV8AtNQrhxpgIMQELc17o08m2iGHV6Lb4GYgHJr
Br/CNav46U4HhLYyCXIbAqYrC6dr7pN83ogBr54T5hjDxD4MClSW3XUFqaWFcMnB9y2V
QQ96jEvU61E19SSy5iO5l2wydh4KPocNvYIdmecoWSBhkrshae3XjJyEq4GObZSpxJs9
wIRnTlIev1MWHwIvVzpOHsY1+lqZj4pF7F9I8IaHFTeFRSLQ+Mh8PTTA7rOBo6qpINUL
UwT1GbZ0zABluv5+gh7ZACc+c6qJf44zWpcwYDk2yLbn/4ZOmb2b1pgz6nQnarEwSeVC
NrkQ==
X-Gm-Message-State: AIVw113Zf/sWAdbN/xvVia4w6Aq6xaUx8o0OEJBjqIG1SenhnZX+VIF4
WbSIc7MQopozU/j9DG0VhylvxVPpowzlC74=
X-Received: by 10.37.246.8 with SMTP id t8mr17412518ybd.120.1501021614717;
Tue, 25 Jul 2017 15:26:54 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Sender: freemanrich@gmail.com
Received: by 10.129.71.3 with HTTP; Tue, 25 Jul 2017 15:26:53 -0700 (PDT)
In-Reply-To: <CAJ0EP43h9tBm+-PrBsv4k=n6RQg0AE_Hdvspjko1OcaCrpE2Tw@mail.gmail.com>
References: <1500969906.1206.1.camel@gentoo.org> <d7063459-69ab-e921-e240-2ab7a6fad40f@gentoo.org>
<0A428688-D128-4767-A9E5-E0F2D3004B18@gentoo.org> <5a155985-1ce4-9872-0259-b67520d9a867@gentoo.org>
<1500988986.795.5.camel@gentoo.org> <a1c6ccda-2053-ad6b-baa9-dd351446087b@gentoo.org>
<CAJ0EP43h9tBm+-PrBsv4k=n6RQg0AE_Hdvspjko1OcaCrpE2Tw@mail.gmail.com>
From: Rich Freeman <rich0@gentoo.org>
Date: Tue, 25 Jul 2017 18:26:53 -0400
X-Google-Sender-Auth: j9ngi9Fx0w5qiIq11Dncvq5AsS8
Message-ID: <CAGfcS_m1Cu2qypEUGtyfEqUQY6OeCT30BoHFHoy6cSLm-Kj4SA@mail.gmail.com>
Subject: Re: [gentoo-dev] [RFC pre-GLEP] Gentoo Git Workflow
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: e13e80d8-5c79-4a43-9377-384af78da128
X-Archives-Hash: 226b82420c8af3cbf286f356e9adedcc
On Tue, Jul 25, 2017 at 4:29 PM, Mike Gilbert <floppym@gentoo.org> wrote:
> On Tue, Jul 25, 2017 at 12:12 PM, Michael Orlitzky <mjo@gentoo.org> wrote=
:
>> On 07/25/2017 09:23 AM, Micha=C5=82 G=C3=B3rny wrote:
>>>
>>> How is that relevant? Revision bumps are merely a tool to encourage
>>> 'automatic' rebuilds of packages during @world upgrade. I can't think o=
f
>>> a single use case where somebody would actually think it sane to
>>> checkout one commit after another, and run @world upgrade in the middle
>>> of it.
>>>
>>
>> Revisions are to indicate that one incarnation of a package differs from
>> another in a way that the user or package manager might care about. And
>> on principal, it's no business of yours what people want to do with
>> their tree. If someone wants to check out successive commits and emerge
>> @world, he's within his rights to do so.
>
> I don't feel I should be obligated by policy to support this use case.
> One revbump per push seems sufficiently safe for 99.9% of users.
>
> If you want to do more revbumps, you are free to do so.
>
What is the point of separating changes by commits if we don't
generally try to keep each commit working?
Sure, there are some cases where it is just going to be too painful to
ensure that, and so it doesn't have to be an absolute rule.
However, if somebody is checking out a tree at some point in the past
they shouldn't have to try to figure out where the last push boundary
was to ensure that it is sane. Use cases for that include updating
older systems progressively, or bisecting a problem.
--=20
Rich