On 02/11/19 08:54, Kent Fredric wrote:
> On Fri, 1 Nov 2019 19:59:35 +
> Michael 'veremitz' Everitt wrote:
>
>> Thoughts from outside peanut gallery?
>>
>> Michael / veremitz.
> I have an alternative that might be more pleasant:
>
> 1. Change repoman so that when its clear that:
>- There i
On Fri, 1 Nov 2019 19:59:35 +
Michael 'veremitz' Everitt wrote:
> Thoughts from outside peanut gallery?
>
> Michael / veremitz.
I have an alternative that might be more pleasant:
1. Change repoman so that when its clear that:
- There is at least one ebuild being changed
- There is on
On Fri, 1 Nov 2019 19:59:35 +
Michael 'veremitz' Everitt wrote:
> Hello,
>
> I've noticed a lot of stabilisation commit messages (and a few keywording
> ones too) simply state the package atom and not the relevant
> release/version. I find this a little meaningless, as unless this is the
> f
On 01/11/19 21:45, Mike Gilbert wrote:
> On Fri, Nov 1, 2019 at 5:34 PM Michael 'veremitz' Everitt
> wrote:
>> On 01/11/19 21:11, Rich Freeman wrote:
>>> On Fri, Nov 1, 2019 at 4:36 PM Matt Turner wrote:
On Fri, Nov 1, 2019 at 12:59 PM Michael 'veremitz' Everitt
wrote:
> Therefore,
On Fri, Nov 1, 2019 at 5:34 PM Michael 'veremitz' Everitt
wrote:
>
> > git log --format=oneline glibc-2.29-r2.ebuild | grep stable
> >
> How well does git handle that when the ebuild is deleted from the tree?
>
git log --format=oneline -- glibc-2.29-r4.ebuild
23d1c015230d9ff44bcdd7b72e00ca3533815
On Fri, Nov 1, 2019 at 5:34 PM Michael 'veremitz' Everitt
wrote:
>
> On 01/11/19 21:11, Rich Freeman wrote:
> > On Fri, Nov 1, 2019 at 4:36 PM Matt Turner wrote:
> >> On Fri, Nov 1, 2019 at 12:59 PM Michael 'veremitz' Everitt
> >> wrote:
> >>>
> >>> Therefore, it would be much /more/ useful to h
On 01/11/19 21:11, Rich Freeman wrote:
> On Fri, Nov 1, 2019 at 4:36 PM Matt Turner wrote:
>> On Fri, Nov 1, 2019 at 12:59 PM Michael 'veremitz' Everitt
>> wrote:
>>>
>>> Therefore, it would be much /more/ useful to have the package-version
>>> tagged in the commit message, so that you could easi
On Fri, Nov 1, 2019 at 4:36 PM Matt Turner wrote:
>
> On Fri, Nov 1, 2019 at 12:59 PM Michael 'veremitz' Everitt
> wrote:
> >
> >
> > Therefore, it would be much /more/ useful to have the package-version
> > tagged in the commit message, so that you could easily grep logs for when a
> > given ver
On Fri, Nov 1, 2019 at 12:59 PM Michael 'veremitz' Everitt
wrote:
>
> Hello,
>
> I've noticed a lot of stabilisation commit messages (and a few keywording
> ones too) simply state the package atom and not the relevant
> release/version. I find this a little meaningless, as unless this is the
> fir
Hello,
I've noticed a lot of stabilisation commit messages (and a few keywording
ones too) simply state the package atom and not the relevant
release/version. I find this a little meaningless, as unless this is the
first time the package has ever been either stabilised or keyworded, it is
reasonab
10 matches
Mail list logo