* primary location of btrfs-progs changelog: The wiki?
@ 2016-04-23 0:41 Nicholas D Steeves
2016-04-23 6:22 ` Duncan
2016-04-25 11:12 ` David Sterba
0 siblings, 2 replies; 8+ messages in thread
From: Nicholas D Steeves @ 2016-04-23 0:41 UTC (permalink / raw)
To: Btrfs BTRFS
Hi,
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).
Sincerely,
Nicholas
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: primary location of btrfs-progs changelog: The wiki?
2016-04-23 0:41 primary location of btrfs-progs changelog: The wiki? Nicholas D Steeves
@ 2016-04-23 6:22 ` Duncan
2016-04-25 11:12 ` David Sterba
1 sibling, 0 replies; 8+ messages in thread
From: Duncan @ 2016-04-23 6:22 UTC (permalink / raw)
To: linux-btrfs
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: primary location of btrfs-progs changelog: The wiki?
2016-04-23 0:41 primary location of btrfs-progs changelog: The wiki? Nicholas D Steeves
2016-04-23 6:22 ` Duncan
@ 2016-04-25 11:12 ` David Sterba
2016-04-25 11:24 ` Nicholas D Steeves
1 sibling, 1 reply; 8+ messages in thread
From: David Sterba @ 2016-04-25 11:12 UTC (permalink / raw)
To: Nicholas D Steeves; +Cc: Btrfs BTRFS
On Fri, Apr 22, 2016 at 08:41:36PM -0400, Nicholas D Steeves wrote:
> 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).
At the moment it's the release announcement in this mailinglist, that
gets copied to the wiki with some formatting adjustments. I'm willing to
copy the announcement text to a file in git (and will do for the next
release). But at the moment I won't add all the past changelogs so if
anybody wants to do that I'l appreciate that.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: primary location of btrfs-progs changelog: The wiki?
2016-04-25 11:12 ` David Sterba
@ 2016-04-25 11:24 ` Nicholas D Steeves
2016-04-25 11:24 ` Nicholas D Steeves
2016-04-25 11:36 ` David Sterba
0 siblings, 2 replies; 8+ messages in thread
From: Nicholas D Steeves @ 2016-04-25 11:24 UTC (permalink / raw)
To: dsterba, Nicholas D Steeves, Btrfs BTRFS
On 25 April 2016 at 07:12, David Sterba <dsterba@suse.cz> wrote:
> On Fri, Apr 22, 2016 at 08:41:36PM -0400, Nicholas D Steeves wrote:
>> I'm just wondering where the primary location of the btrfs-progs
>> changelog is located
>
> At the moment it's the release announcement in this mailinglist, that
> gets copied to the wiki with some formatting adjustments. I'm willing to
> copy the announcement text to a file in git (and will do for the next
> release). But at the moment I won't add all the past changelogs so if
> anybody wants to do that I'l appreciate that.
I'd be happy to. Are you looking for something like:
curl https://btrfs.wiki.kernel.org/index.php/Changelog | html2text |
sed '0,/(announcement)/d;/By version (linux kernel)/Q' | gzip -9 >
changelog
With some formatting adjustments?
Cheers,
Nicholas
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: primary location of btrfs-progs changelog: The wiki?
2016-04-25 11:24 ` Nicholas D Steeves
@ 2016-04-25 11:24 ` Nicholas D Steeves
2016-04-25 11:36 ` David Sterba
1 sibling, 0 replies; 8+ messages in thread
From: Nicholas D Steeves @ 2016-04-25 11:24 UTC (permalink / raw)
To: dsterba, Nicholas D Steeves, Btrfs BTRFS
oops, that gzip -9 shouldn't be there :-/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: primary location of btrfs-progs changelog: The wiki?
2016-04-25 11:24 ` Nicholas D Steeves
2016-04-25 11:24 ` Nicholas D Steeves
@ 2016-04-25 11:36 ` David Sterba
2016-04-25 12:06 ` Nicholas D Steeves
1 sibling, 1 reply; 8+ messages in thread
From: David Sterba @ 2016-04-25 11:36 UTC (permalink / raw)
To: Nicholas D Steeves; +Cc: dsterba, Btrfs BTRFS
On Mon, Apr 25, 2016 at 07:24:27AM -0400, Nicholas D Steeves wrote:
> On 25 April 2016 at 07:12, David Sterba <dsterba@suse.cz> wrote:
> > On Fri, Apr 22, 2016 at 08:41:36PM -0400, Nicholas D Steeves wrote:
> >> I'm just wondering where the primary location of the btrfs-progs
> >> changelog is located
> >
> > At the moment it's the release announcement in this mailinglist, that
> > gets copied to the wiki with some formatting adjustments. I'm willing to
> > copy the announcement text to a file in git (and will do for the next
> > release). But at the moment I won't add all the past changelogs so if
> > anybody wants to do that I'l appreciate that.
>
> I'd be happy to. Are you looking for something like:
>
> curl https://btrfs.wiki.kernel.org/index.php/Changelog | html2text |
> sed '0,/(announcement)/d;/By version (linux kernel)/Q' | gzip -9 >
> changelog
>
> With some formatting adjustments?
The conversion looks relatively ok, indentation could be 2 spaces and
all bullet lists with '*'. Thanks.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: primary location of btrfs-progs changelog: The wiki?
2016-04-25 11:36 ` David Sterba
@ 2016-04-25 12:06 ` Nicholas D Steeves
2016-04-25 13:50 ` David Sterba
0 siblings, 1 reply; 8+ messages in thread
From: Nicholas D Steeves @ 2016-04-25 12:06 UTC (permalink / raw)
To: dsterba, Nicholas D Steeves, Btrfs BTRFS
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
On 25 April 2016 at 07:36, David Sterba <dsterba@suse.cz> wrote:
> The conversion looks relatively ok, indentation could be 2 spaces and
> all bullet lists with '*'. Thanks.
Done. I also added one line before each new version. I've attached
it, since it's just one file; however, if you prefer I can clone your
repo on github and submit it that way.
Cheers,
Nick
[-- Attachment #2: changelog.gz --]
[-- Type: application/x-gzip, Size: 6455 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: primary location of btrfs-progs changelog: The wiki?
2016-04-25 12:06 ` Nicholas D Steeves
@ 2016-04-25 13:50 ` David Sterba
0 siblings, 0 replies; 8+ messages in thread
From: David Sterba @ 2016-04-25 13:50 UTC (permalink / raw)
To: Nicholas D Steeves; +Cc: dsterba, Btrfs BTRFS
On Mon, Apr 25, 2016 at 08:06:47AM -0400, Nicholas D Steeves wrote:
> On 25 April 2016 at 07:36, David Sterba <dsterba@suse.cz> wrote:
> > The conversion looks relatively ok, indentation could be 2 spaces and
> > all bullet lists with '*'. Thanks.
>
> Done. I also added one line before each new version. I've attached
> it, since it's just one file; however, if you prefer I can clone your
> repo on github and submit it that way.
Thanks. I had a look how a changes file is usually formatted and made
further changes: fixed ordering of the minor releases, added exact dates
of release and un-indented in a few more places, plus some minor fixes.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2016-04-25 13:50 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-04-23 0:41 primary location of btrfs-progs changelog: The wiki? Nicholas D Steeves
2016-04-23 6:22 ` Duncan
2016-04-25 11:12 ` David Sterba
2016-04-25 11:24 ` Nicholas D Steeves
2016-04-25 11:24 ` Nicholas D Steeves
2016-04-25 11:36 ` David Sterba
2016-04-25 12:06 ` Nicholas D Steeves
2016-04-25 13:50 ` David Sterba
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.