Re: primary location of btrfs-progs changelog: The wiki?

[Duncan <1i5t5.duncan@cox.net>]

Nicholas D Steeves posted on Fri, 22 Apr 2016 20:41:36 -0400 as excerpted:

> I'm just wondering where the primary location of the btrfs-progs
> changelog is located, because I'd like to include upstream changes in
> the Debian package.  Is it really the wiki?  If so, it would seem my
> options are copying+pasting with every release, or writing a script to
> download the page, convert it to text, and then do something like cut
> everything before By version (btrfs-progs) and everything after By
> version (linux kernel).

As with most modern projects, particularly those that are kernel related, 
I believe the _primary_ and authoritative changelog is git log. =:^)  
Particularly with the kernel, Linus's merge-commits for the various 
subsystems (btrfs in this case) tend to give a rather good if somewhat 
technical overview of what's going on with the whole merge, so you don't 
need to drill down to individual commits unless it's something you're 
/that/ interested in.

Beyond git log and other than the wiki, for userspace see the "Btrfs progs 
release" (that should be a reasonable subject search on any of the list 
archives, or use pre-release if you want them) messages authored by David 
Sterba here on this list.  They normally contain a reasonable "user-
level" summary, similar to what eventually gets put on the wiki (indeed, 
I'd guess the wiki copies from the release announcements).

For example:

http://permalink.gmane.org/gmane.comp.file-systems.btrfs/54781

For the kernel, search on "[GIT PULL] Btrfs" messages from Chris Mason.  
For example:

http://permalink.gmane.org/gmane.linux.kernel/219422

As with many subsystems Linus often uses these pretty directly in his 
merge commit comments, so it's pretty close to the same thing you'd get 
by reading the git log merge commits.

But beyond that, I think it's the wiki, which I believe can also have 
slightly more mainstreamed/sysadmin-level-change descriptions, 
particularly for the kernel, as I believe they're edited a bit 
differently than the git pull notices, where Linus and git log readers 
are the primary audience.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman