| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 01-06-2011 19:50, Nirbheek Chauhan wrote: |
| 5 |
> On Wed, Jun 1, 2011 at 9:54 PM, Andreas K. Huettel <dilfridge@g.o> wrote: |
| 6 |
>> |
| 7 |
>>> So we come back to the problem being *CVS* not ChangeLog rules. |
| 8 |
>> |
| 9 |
>> Well of course we can just tell everyone "go look it up on sources.gentoo.org". |
| 10 |
>> However, this is a different discussion. |
| 11 |
>> |
| 12 |
> sources.gentoo.org is a much worse (and slower) solution than cvs log. |
| 13 |
> The main advantage of a ChangeLog (and of git) is that it allows you |
| 14 |
> to check the history locally, without needing access to the network. |
| 15 |
> |
| 16 |
>>> All this is such a massive waste of time. Can't we just expend this |
| 17 |
>>> energy on the move to git? |
| 18 |
>> |
| 19 |
> [snip] |
| 20 |
>> We're not talking about future plans here but about the current situation. |
| 21 |
>> And about how to deal with it. |
| 22 |
>> |
| 23 |
> |
| 24 |
> The current situation is: |
| 25 |
> |
| 26 |
> (a) Not dire. |
| 27 |
> (b) Not urgent. |
| 28 |
|
| 29 |
(c) has irked enough developers and users that people pushed council to |
| 30 |
update the policy about the use of ChangeLogs. |
| 31 |
|
| 32 |
> And if we decide, hey, let's move to git instead of having this |
| 33 |
> discussion, the current situation is also: |
| 34 |
> |
| 35 |
> (c) A waste of everyone's time. |
| 36 |
> |
| 37 |
> So no, future plans are not independent of the current situation, and |
| 38 |
> a move to git *is* a way to deal with the current situation. |
| 39 |
> |
| 40 |
> In effect, we kill (at least) two birds with one stone and prevent a |
| 41 |
> lot of argument and bad blood. |
| 42 |
|
| 43 |
To be clear I support the goal to move our tree to git. |
| 44 |
However, I'd like to point out that simply moving to git will leave us |
| 45 |
in the same state. Assuming everyone agrees that git is far more useful |
| 46 |
than cvs to check for changes in the tree, a simple but important issue |
| 47 |
remains: the plan is to move the "development tree" to git, but to keep |
| 48 |
the rsync mirrors for users. So the "move to git" doesn't fix the issue |
| 49 |
for users or developers using an rsync tree. |
| 50 |
One solution that has been proposed before and that was raised again in |
| 51 |
this thread is to generate ChangeLogs directly from scm commit messages. |
| 52 |
That is already a solution with cvs, so moving to git won't help here. |
| 53 |
The same objections that have been raised about doing it for cvs, not |
| 54 |
being able to use different messages for the commit message and in |
| 55 |
ChangeLog (something I understand but admit have hardly used before), |
| 56 |
are also valid if we move to git. |
| 57 |
|
| 58 |
- -- |
| 59 |
Regards, |
| 60 |
|
| 61 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
| 62 |
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng |
| 63 |
-----BEGIN PGP SIGNATURE----- |
| 64 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 65 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 66 |
|
| 67 |
iQIcBAEBAgAGBQJN5stWAAoJEC8ZTXQF1qEPIPMQAJOBJxGkWJZ3saNdQvAjbR7l |
| 68 |
KQdLHbO3IdUTBixqSqnmBXop4d6XFBd6lZyjiLu29x9xBn68wE4gm7rlpulITs6R |
| 69 |
Yqh4ASyLkUF88qezmqdkBaIy/TUGpGS7ZQWMu7ViarhPtLpcyrVWIh8U0T7oJZBh |
| 70 |
offLYHiQK9dDajLro83aIGLfRlLEYTB9MhjHegv8sDTUCr+ti23OuKjO0CoI7LFx |
| 71 |
yYdnzkA1YQWA1MGj6iEAVHzcy+RsaGK1QfVn26qAyly3Mg4mPkbKjtIHUEleIV0X |
| 72 |
TiWPQfNOvPbbNNyuaJ2cBZoGSTLtTstwUKMccYspQawCpDz0h2yNxNLtVS5ws5AO |
| 73 |
HBvfuWROKtWQ90hSiHb5dy13KXhRYR0CZzGPPLMs316YzdsFtKRL5AG3ywzLT2Bu |
| 74 |
Dj/wiUoRIRhoPuBTRskCxmXBd04nE/MtDZM/MRn0OZE9zHeYvZYIqCtWVXaGejtZ |
| 75 |
uID3LxOdGvJn07+TeH7/i8ap4zchRvwZaW6H9LBFr5bIHzKEFPUAfL3NqquGj66d |
| 76 |
HOHsh/RdPG25gKAZy5/zJ92lsRbFyZlxZFNYoTBTSFg89z7YldPMMxPPpNMWro+n |
| 77 |
ZzhyourKYprtt2+ZI05gPB/f24KMBhZY8kALoORSeNpUxBwTQ/aanpbKKqjFcfuv |
| 78 |
j0asDqRgkHAvpF3aTmaI |
| 79 |
=cSzK |
| 80 |
-----END PGP SIGNATURE----- |
Archives