1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA512 |
3 |
|
4 |
Ulrich Mueller: |
5 |
>>>>>> On Sun, 24 Jan 2016, Michael Orlitzky wrote: |
6 |
> |
7 |
>> The ChangeLog page is nonsense as-is, and removing it makes the |
8 |
>> devmanual better. Afterwards, if someone wants to take the commit |
9 |
>> message guidelines from the wiki and merge them with the old |
10 |
>> ChangeLog tips, great. There's only two things worth salvaging |
11 |
>> from the ChangeLog page. Here's the combined list: |
12 |
> |
13 |
>> 1. Everything from the Git workflow wiki page "Commit message |
14 |
>> format" section. |
15 |
> |
16 |
> I would say not only that section, but most of the page. The |
17 |
> devmanual is the one central place where our development workflow |
18 |
> should be documented, not some random wiki page. |
19 |
> |
20 |
If the most up-to-date information is on the wiki, constantly updating |
21 |
devmanual to match the wiki creates unnecessary maintenance burden. |
22 |
|
23 |
>> 2. Mention the "Gentoo-Bug:" identifier. |
24 |
> |
25 |
> Right. (But had we settled for "Gentoo-Bug:"? IIRC, last time this |
26 |
> was discussed there was no consensus.) |
27 |
> |
28 |
Related to my point above, looks like the git workflow is still in the |
29 |
process of making. I expect that some discussion will continue to take |
30 |
place in the future. We can always fix the other parts of the |
31 |
devmanual and come back to this. |
32 |
|
33 |
Is it possible to merge this changeset as is while the workflow |
34 |
matures, or should I go for a round 3? |
35 |
|
36 |
>> Using "bug #12345" in the commit message itself causes trouble. |
37 |
>> If you word-wrap on the "#12345", it will silently clobber the |
38 |
>> message. |
39 |
> |
40 |
> That's one of the reasons why I have 'commentchar = ";"' in my |
41 |
> .gitconfig file. (Not sure if that option would be worth mentioning |
42 |
> in our documentation, though.) |
43 |
> |
44 |
>> [...] |
45 |
> |
46 |
> Ulrich |
47 |
> |
48 |
|
49 |
- -- |
50 |
gokturk |
51 |
|
52 |
-----BEGIN PGP SIGNATURE----- |
53 |
|
54 |
iQEcBAEBCgAGBQJWqEU2AAoJEIT4AuXAiM4zwCAH/3q8FQB+zX0q1kuXjJfYnF3j |
55 |
IvJ2uKjuHMfbSAoGy2bUGEEhsvXGpNTmLv7vDIiHILCeLR0mD1eAmWHuJjjUSmJx |
56 |
PyK6kAPaXX++E5aZ9gRuXqNFSGqiNx3oPvzQs0SH6vXgVec8fpmRk6y/Dg2r20Am |
57 |
hfJLPIeD8Z9Vf/0wM7EcjiS3eVYrTnYCX+aGAKpgk74zKHcnHTL9S77no0Lemby1 |
58 |
vlCK9ceouVd6OYdDcvjNg73umlci7JIenCZCU3nagloGwvH6XDFWdGkWSRLQ0G7T |
59 |
DoZlysM2Litafjr7NgyQ7R8xp1HnR+tmWfY26urIPd4rKU+aA05kPnQiTjgKTHo= |
60 |
=UDYD |
61 |
-----END PGP SIGNATURE----- |