-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01-06-2011 19:50, Nirbheek Chauhan wrote:
> On Wed, Jun 1, 2011 at 9:54 PM, Andreas K. Huettel <dilfridge@g.o> wrote:
>>
>>> So we come back to the problem being *CVS* not ChangeLog rules.
>>
>> Well of course we can just tell everyone "go look it up on sources.gentoo.org".
>> However, this is a different discussion.
>>
> sources.gentoo.org is a much worse (and slower) solution than cvs log.
> The main advantage of a ChangeLog (and of git) is that it allows you
> to check the history locally, without needing access to the network.
>
>>> All this is such a massive waste of time. Can't we just expend this
>>> energy on the move to git?
>>
> [snip]
>> We're not talking about future plans here but about the current situation.
>> And about how to deal with it.
>>
>
> The current situation is:
>
> (a) Not dire.
> (b) Not urgent.
(c) has irked enough developers and users that people pushed council to
update the policy about the use of ChangeLogs.
> And if we decide, hey, let's move to git instead of having this
> discussion, the current situation is also:
>
> (c) A waste of everyone's time.
>
> So no, future plans are not independent of the current situation, and
> a move to git *is* a way to deal with the current situation.
>
> In effect, we kill (at least) two birds with one stone and prevent a
> lot of argument and bad blood.
To be clear I support the goal to move our tree to git.
However, I'd like to point out that simply moving to git will leave us
in the same state. Assuming everyone agrees that git is far more useful
than cvs to check for changes in the tree, a simple but important issue
remains: the plan is to move the "development tree" to git, but to keep
the rsync mirrors for users. So the "move to git" doesn't fix the issue
for users or developers using an rsync tree.
One solution that has been proposed before and that was raised again in
this thread is to generate ChangeLogs directly from scm commit messages.
That is already a solution with cvs, so moving to git won't help here.
The same objections that have been raised about doing it for cvs, not
being able to use different messages for the commit message and in
ChangeLog (something I understand but admit have hardly used before),
are also valid if we move to git.
- --
Regards,
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJN5stWAAoJEC8ZTXQF1qEPIPMQAJOBJxGkWJZ3saNdQvAjbR7l
KQdLHbO3IdUTBixqSqnmBXop4d6XFBd6lZyjiLu29x9xBn68wE4gm7rlpulITs6R
Yqh4ASyLkUF88qezmqdkBaIy/TUGpGS7ZQWMu7ViarhPtLpcyrVWIh8U0T7oJZBh
offLYHiQK9dDajLro83aIGLfRlLEYTB9MhjHegv8sDTUCr+ti23OuKjO0CoI7LFx
yYdnzkA1YQWA1MGj6iEAVHzcy+RsaGK1QfVn26qAyly3Mg4mPkbKjtIHUEleIV0X
TiWPQfNOvPbbNNyuaJ2cBZoGSTLtTstwUKMccYspQawCpDz0h2yNxNLtVS5ws5AO
HBvfuWROKtWQ90hSiHb5dy13KXhRYR0CZzGPPLMs316YzdsFtKRL5AG3ywzLT2Bu
Dj/wiUoRIRhoPuBTRskCxmXBd04nE/MtDZM/MRn0OZE9zHeYvZYIqCtWVXaGejtZ
uID3LxOdGvJn07+TeH7/i8ap4zchRvwZaW6H9LBFr5bIHzKEFPUAfL3NqquGj66d
HOHsh/RdPG25gKAZy5/zJ92lsRbFyZlxZFNYoTBTSFg89z7YldPMMxPPpNMWro+n
ZzhyourKYprtt2+ZI05gPB/f24KMBhZY8kALoORSeNpUxBwTQ/aanpbKKqjFcfuv
j0asDqRgkHAvpF3aTmaI
=cSzK
-----END PGP SIGNATURE-----
|
