From: Jacob Keller <jacob.e.keller@intel.com>
To: git@vger.kernel.org
Cc: Jacob Keller <jacob.keller@gmail.com>
Subject: [PATCH v2 0/2] notes: add notes.merge strategy option
Date: Fri, 31 Jul 2015 16:12:19 -0700 [thread overview]
Message-ID: <1438384341-2688-1-git-send-email-jacob.e.keller@intel.com> (raw)
From: Jacob Keller <jacob.keller@gmail.com>
This series adds a default merge strategy option for git-notes, so that
the user does not have to type "-s" every time. It is overridden by the
-s option.
I also added some tests to ensure that the "--abort" "--commit" and "-s"
options must be independent. In addition, I found a small documentation
bug which is corrected in the first patch of the series.
I Cc'd a couple more people in this version of the patch in order to
hopefully get some more review. This is based on pu incase there were
any other conflicts, but I can easily rebase if necessary.
Jacob Keller (2):
notes: document cat_sort_uniq rewriteMode
notes: add notes.merge option to select default strategy
Documentation/config.txt | 11 +++++--
Documentation/git-notes.txt | 33 +++++++++++++--------
builtin/notes.c | 55 +++++++++++++++++++++++++----------
notes-merge.h | 16 +++++-----
t/t3309-notes-merge-auto-resolve.sh | 29 ++++++++++++++++++
t/t3310-notes-merge-manual-resolve.sh | 12 ++++++++
6 files changed, 119 insertions(+), 37 deletions(-)
--
2.5.0.482.gfcd5645
next reply other threads:[~2015-07-31 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 23:12 Jacob Keller [this message]
2015-07-31 23:12 ` [PATCH v2 1/2] notes: document cat_sort_uniq rewriteMode Jacob Keller
2015-07-31 23:12 ` [PATCH v2 2/2] notes: add notes.merge option to select default strategy Jacob Keller
2015-08-02 2:46 ` Eric Sunshine
2015-08-02 4:12 ` Jacob Keller
2015-08-02 7:41 ` Jacob Keller
2015-08-02 8:01 ` Eric Sunshine
2015-08-02 8:20 ` Jacob Keller
2015-08-01 13:30 ` [PATCH v2 0/2] notes: add notes.merge strategy option Johan Herland
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=1438384341-2688-1-git-send-email-jacob.e.keller@intel.com \
--to=jacob.e.keller@intel.com \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
/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).