1 |
On 10/19/2015 07:52 PM, Rich Freeman wrote: |
2 |
> On Mon, Oct 19, 2015 at 1:40 PM, hasufell <hasufell@g.o> wrote: |
3 |
>> On 10/19/2015 07:37 PM, Rich Freeman wrote: |
4 |
>>> |
5 |
>>> However, stabilizing a single package really is an impactful change. |
6 |
>>> The fact that you're doing 100 of them at one time doesn't really |
7 |
>>> diminish the impact of each one. Any of them could break a system or |
8 |
>>> need to be reverted. |
9 |
>>> |
10 |
>> |
11 |
>> Since when do we allow reverting stabilization? The package needs to be |
12 |
>> fixed and possibly revbumped instead. |
13 |
>> |
14 |
> |
15 |
> It would really depend on the nature of the break. If it is a serious |
16 |
> upstream problem and no fix is available, then reverting might be the |
17 |
> only practical solution. It is of course not a preferred solution. |
18 |
> |
19 |
|
20 |
I don't think we depend on 'git revert' in that case. KEYWORDS are |
21 |
trivial changes (in terms of file diffs). |