Isolating the packaging changes is hardly difficult:
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-shirou-gopsutil.git/log/debian

On 24 June 2016 at 05:52, Dmitry Smirnov <only...@debian.org> wrote:
> On Tuesday, 21 June 2016 6:32:46 PM AEST Martín Ferrari wrote:
>> On 20/06/16 05:11, Dmitry Smirnov wrote:
>> > I do not mind having full upstream history in "upstream"
>> > branch but not in "master"...
>> I don't really have any issue with having all the
>> commits, as it is pretty clear to me which ones belong to debian,
>
> I found it hard to believe. Looking at commit log [1], how many pages you
> need to skip to find packaging commits prior to merge of last upstream
> release to master? This is not the worst case as upstream is not too active
> but there are projects with thousands of commits between releases...
> All git GUIs are affected because those commits are obstructing.
> Besides depending on git GUI it may be not so clear which commits are
> related to packaging...
>
> [1]: 
> https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-shirou-gopsutil.git/log/
>
> --
> Regards,
>  Dmitry Smirnov.
>
> ---
>
> A creative man is motivated by the desire to achieve, not by the desire
> to beat others.
>         -- Ayn Rand
>
> _______________________________________________
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to