| 1 |
On Fri, Aug 28, 2015 at 11:26 AM, James <wireless@×××××××××××.com> wrote: |
| 2 |
> I agree with this. But since the Changlog data was a fundamental part |
| 3 |
> of Gentoo, for a very long time, and the devs wisely chose to upgrade |
| 4 |
> to git, I would think that this functionality would be provided |
| 5 |
> via git, at least by some hacks or detailed example. |
| 6 |
|
| 7 |
See my email, and the follow-up with the repos.conf for fetching from git. |
| 8 |
|
| 9 |
I'm sure the docs will continue to evolve, and changelogs may be |
| 10 |
re-introduced in rsync. |
| 11 |
|
| 12 |
> In the meantime WE, the gentoo users should |
| 13 |
> not be required to study git and roll our own solution, one at a time from |
| 14 |
> previously well defined functionality, imho. Besides Git is |
| 15 |
> quite a beast:: how long from inception to completion did the gentoo git |
| 16 |
> migration take? years? a decade? |
| 17 |
|
| 18 |
If you give it a few months I'm sure everything will settle out. |
| 19 |
|
| 20 |
We've taken WAY too long to complete the git migration, and most of |
| 21 |
the delay was in the interest of avoiding impacting users with change. |
| 22 |
We basically ended up drawing a line in the sand and saying that we |
| 23 |
knew there would be little issues like this that annoy some people to |
| 24 |
no end, and we'll just deal with that. Otherwise it would have been |
| 25 |
another 5 years before we end up cancelling the git migration and |
| 26 |
started talking about whatever is replacing git. |
| 27 |
|
| 28 |
> But that's exactly the point; for Changelogs and such info, there |
| 29 |
> should at least be a news item or dev-blog post on automating such |
| 30 |
> things. Per packages solutions miss the point of convenience of Changelogs. |
| 31 |
|
| 32 |
Feel free to contribute a news item or blog post. :) |
| 33 |
|
| 34 |
And nobody is proposing any per-package solutions. Git covers the |
| 35 |
entire tree and we've standardized the commit messages/etc. |
| 36 |
|
| 37 |
> Enhanced data beyond changelogs? Sure, but that caveat should not be |
| 38 |
> a blocker to what was available. ymmv. |
| 39 |
|
| 40 |
Sure, and those old-format changelogs will probably exist again some |
| 41 |
day. If more people find them useful, they're more likely to get |
| 42 |
re-created. |
| 43 |
|
| 44 |
-- |
| 45 |
Rich |
Archives