| 1 |
On 11/01/2015 01:16 PM, Patrick Lauer wrote: |
| 2 |
> Ahoi, |
| 3 |
> |
| 4 |
> I'm getting mildly very irritated with the lack of easily accessible |
| 5 |
> ChangeLogs for our packages. |
| 6 |
> |
| 7 |
> Apparently updating them stopped some time in August, so now there are |
| 8 |
> some outdated ChangeLogs that don't really serve any purpose, and the |
| 9 |
> easiest way for users to figure out why something changed is to yell at |
| 10 |
> the clumsy gitweb.g.o interface. So instead of grep we now need lots of |
| 11 |
> patience. |
| 12 |
> |
| 13 |
> This does not look reasonable to me. |
| 14 |
> |
| 15 |
> Can we please either properly remove ChangeLogs and tell people to not |
| 16 |
> be curious about changes, or make them useful again? |
| 17 |
> |
| 18 |
|
| 19 |
|
| 20 |
ChangeLogs are a deprecated and unreliable method of the times we were |
| 21 |
still on CVS. E.g. some people didn't find it useful to add ChangeLog |
| 22 |
entries when they did large eclass changes. This problem is gone now. |
| 23 |
|
| 24 |
git log -- app-misc/foo |
| 25 |
or |
| 26 |
git log -- eclass/autotools.eclass |
| 27 |
|
| 28 |
will give you _any_ commit that has touched that file/directory, even if |
| 29 |
it was part of a huge mass commit. |
| 30 |
|
| 31 |
There's really not much ChangeLogs add for you here, except duplicating |
| 32 |
git functionality. It's more useful to familiarize yourself with git |
| 33 |
log. There's no reason to depend on the gitweb interface. |
| 34 |
|
| 35 |
If you want the history from before the migration to work with that as |
| 36 |
well, you can use this method: |
| 37 |
https://wiki.gentoo.org/wiki/Gentoo_git_workflow#Grafting_Gentoo_History_Onto_the_Active_Repo |
| 38 |
|
| 39 |
Also see |
| 40 |
https://www.atlassian.com/git/tutorials/git-log/filtering-the-commit-history |
Archives