Re: Fetching or installing package dev source from VCS: manual style

[Philip Kaludercic]

Rudolf Adamkovič <salutis@me.com> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> [...]  This might be inadequate if you wish to hack on the package
>> sources and add new features.
>
> I will let *you* cook. :)  One last quick comment:
>
> The new version says "hack on the package sources and add new features",
> but someone might want to fix a bug, perhaps a typo, not add a new
> feature.  Or they might want to simply read the code to learn!  The old
> version said it much more *beautifully*, "hack on the source code of a
> package, and perhaps share your changes with others".

How about "hack on the package sources and add new features to share
with others"?

>> It wouldn't be difficult to integrate 'vc-log-incoming' into some
>> command like 'package-vc-whats-new'.
>
> We would still need wire that up to e.g. 'package-update-all' so that it
> shows What's New for *all* packages instead of, wait for it, ...
>
> One package to update.  Do it? (y or n)

Hmm, I see what you mean but I don't know if this is a good idea in
general when using `package-update-all' to have a log buffer pop up for
every package.

> :-)
>
> Rudy