From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 1/2] btrfs-progs: copy functionality of btrfs-debug-tree to inspect-internal subcommand
Date: Tue, 23 Feb 2016 00:43:58 +0000 (UTC) [thread overview]
Message-ID: <pan$4efde$cf821d81$2d3ab60d$a3a7e1a8@cox.net> (raw)
In-Reply-To: 1456152590-24601-1-git-send-email-fougner89@gmail.com
Alexander Fougner posted on Mon, 22 Feb 2016 15:49:49 +0100 as excerpted:
> The long-term plan is to merge the features of standalone tools into the
> btrfs binary, reducing the number of shipped binaries.
>
> Signed-off-by: Alexander Fougner <fougner89@gmail.com>
> ---
Typically, V2+ also includes a short, often one-line, description of what
changed between versions. This helps reviewers and others who may have
reviewed/tested previous versions, or who may simply be interested in
following the evolution of the patch as it improves toward acceptance and
merging, since it avoids everyone having to do the diffs for themselves.
It's also useful to others who may be considering submitting their own
patches, since it can give them hints on avoiding some of the same
initial mistakes and thus avoiding a round-trip or two, as they may be
able to correct some of the issues before they post their patches the
first time (or the second time, if they notice the practice of including
the changes description on existing patch revision posts and include it
themselves without anyone having to ask). =:^)
Unfortunately, while the subject says v2, I don't see any such changes
since v1 description, here. =:^(
There's many examples on the list if you need one. Here's a link to the
first one I happened to find, a good example of how it can look on
slightly more advanced patch series of several patches, once they've gone
thru several revisions. (Click the topic link on the left to see the
individual patches, which here don't include individual changelogs as
they're in the 00/19 post.)
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/53306
--
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
next prev parent reply other threads:[~2016-02-23 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 14:49 [PATCH v2 1/2] btrfs-progs: copy functionality of btrfs-debug-tree to inspect-internal subcommand Alexander Fougner
2016-02-22 14:49 ` [PATCH v2 2/2] btrfs-progs: update docs and completion for inspect-internal dump-tree Alexander Fougner
2016-02-23 0:43 ` Duncan [this message]
2016-02-23 18:05 ` [PATCH v2 1/2] btrfs-progs: copy functionality of btrfs-debug-tree to inspect-internal subcommand David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$4efde$cf821d81$2d3ab60d$a3a7e1a8@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).