1 |
On 5/8/16 8:34 AM, Rich Freeman wrote: |
2 |
> On Sun, May 8, 2016 at 8:18 AM, Kent Fredric <kentfredric@×××××.com> wrote: |
3 |
>> On 9 May 2016 at 00:09, Anthony G. Basile <blueness@g.o> wrote: |
4 |
>>> 1. announce to gentoo-dev@ the intention to start a branch intending to |
5 |
>>> merge |
6 |
>>> |
7 |
>>> 2. hack hack hack |
8 |
>>> |
9 |
>>> 3. test the merge for any conflicts etc, |
10 |
>>> |
11 |
>>> 4. announce to the list a date/time to merge |
12 |
>>> |
13 |
>>> 5. if okay, ermge |
14 |
>> |
15 |
>> It would make much sense for this series to be visible on Master as a |
16 |
>> "add Perl 5.24 to tree" commit, because all the changes are inherently |
17 |
>> interdependent, |
18 |
>> and it would make little sense to rewind to a specific point within |
19 |
>> that series and use it as a portage tree. |
20 |
>> |
21 |
>> But that's not significant enough to warrant a lot of formal fluffing around. |
22 |
>> |
23 |
>> It for sure would be best if that 100 commit range was rebased before |
24 |
>> merging, but it should still be a non-fast-forward merge just to keep |
25 |
>> the history logical. |
26 |
>> |
27 |
> |
28 |
> ++ |
29 |
> |
30 |
> merges shouldn't just be used for random pull-requests. However, when |
31 |
> you're touching multiple packages/etc they should be considered. |
32 |
|
33 |
i was actually thinking of sec-policy where i remember writing a script |
34 |
back in the CVS days that did some 200 commits, one after another. i |
35 |
was migrating some work for Swift from an overlay to the main tree. |
36 |
|
37 |
|
38 |
They |
39 |
> should also be considered if for some reason you had a bazillion |
40 |
> commits to a single package that for some reason shouldn't be rebased. |
41 |
|
42 |
a bazillion commits to a category that almost no one touches and except |
43 |
one person or team, like sec-policy or dev-perl etc. |
44 |
|
45 |
so again, i'm against an outright banning of merge commits, but we need |
46 |
to restrict them to reasonable cases, "reasonable" being judged by the |
47 |
community. |
48 |
|
49 |
> I imagine that they'll be a small portion of commits as a result. |
50 |
> However, for the situations where they're appropriate they make a lot |
51 |
> of sense. |
52 |
> |
53 |
> This was some of Duncan's point, but I will comment that we'll never |
54 |
> have as clean a history as the kernel simply because we don't have a |
55 |
> release-based workflow with the work cascading up various trees. The |
56 |
> kernel is almost an ideal case for a merge-based workflow. I imagine |
57 |
> that half of Gentoo's commit volume is random revbumps and keyword |
58 |
> changes and that is just going to be noise no matter what. If we were |
59 |
> release-based we could do that stuff in its own branch and merge it |
60 |
> all in at once, but that just isn't us. |
61 |
> |
62 |
> -- |
63 |
> Rich |
64 |
> |
65 |
|
66 |
|
67 |
-- |
68 |
Anthony G. Basile, Ph.D. |
69 |
Gentoo Linux Developer [Hardened] |
70 |
E-Mail : blueness@g.o |
71 |
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA |
72 |
GnuPG ID : F52D4BBA |