From: Johan Herland <johan@herland.net>
To: Stephen Boyd <bebarino@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [WIP/RFC 13/13] Documentation: Preliminary docs on 'git notes merge'
Date: Sun, 25 Jul 2010 21:02:52 +0200 [thread overview]
Message-ID: <201007252102.52632.johan@herland.net> (raw)
In-Reply-To: <4C4AA297.4090605@gmail.com>
On Saturday 24 July 2010, Stephen Boyd wrote:
> On 07/23/2010 03:15 AM, Johan Herland wrote:
> > +-X<strategy>::
> > +--resolve=<strategy>::
> > + When merging notes, resolve notes conflicts using the given
> > + strategy. The following strategies are recognized: "manual"
> > + (default), "ours", "theirs" and "union". "ours" automatically
> > + resolves conflicting notes in favor of the local version (i.e.
> > + the current notes ref). "theirs" auto-resolves notes conflicts
> > + in favor of the remote version (i.e. the given notes ref being
> > + merged into the current notes ref). "union" auto-resolves
> > + notes conflicts by concatenating the local and remote versions.
> > +
>
> We use both "auto-resolves" and "automatically resolves" in this
> paragraph. Perhaps it's better to use one term throughout?
Agreed. I'll squash the following into the next iteration:
...Johan
diff --git a/Documentation/git-notes.txt b/Documentation/git-notes.txt
index f4ad4cc..9228349 100644
--- a/Documentation/git-notes.txt
+++ b/Documentation/git-notes.txt
@@ -90,8 +90,9 @@ merge::
notes ref (called "remote") since the merge-base (if
any) into the current notes ref (called "local").
+
-If conflicts arise (and a strategy for auto-resolving conflicting notes
-(see the -X/--resolve option) is not given, the merge fails (TODO).
+If conflicts arise (and a strategy for automatically resolving
+conflicting notes (see the -X/--resolve option) is not given,
+the merge fails (TODO).
remove::
Remove the notes for a given object (defaults to HEAD).
@@ -146,12 +147,14 @@ OPTIONS
--resolve=<strategy>::
When merging notes, resolve notes conflicts using the given
strategy. The following strategies are recognized: "manual"
- (default), "ours", "theirs" and "union". "ours" automatically
- resolves conflicting notes in favor of the local version (i.e.
- the current notes ref). "theirs" auto-resolves notes conflicts
- in favor of the remote version (i.e. the given notes ref being
- merged into the current notes ref). "union" auto-resolves
- notes conflicts by concatenating the local and remote versions.
+ (default), "ours", "theirs" and "union".
+ "ours" automatically resolves conflicting notes in favor of the
+ local version (i.e. the current notes ref).
+ "theirs" automatically resolves notes conflicts in favor of the
+ remote version (i.e. the given notes ref being merged into the
+ current notes ref).
+ "union" automatically resolves notes conflicts by concatenating
+ the local and remote versions.
-q::
--quiet::
--
Johan Herland, <johan@herland.net>
www.herland.net
next prev parent reply other threads:[~2010-07-25 19:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 10:14 [WIP/RFC 00/13] git notes merge Johan Herland
2010-07-23 10:14 ` [WIP/RFC 01/13] (trivial) notes.h: Minor documentation fixes to copy_notes() Johan Herland
2010-07-23 10:14 ` [WIP/RFC 02/13] notes.h: Make default_notes_ref() available in notes API Johan Herland
2010-07-23 10:14 ` [WIP/RFC 03/13] notes.h/c: Clarify the handling of notes objects that are == null_sha1 Johan Herland
2010-07-23 10:14 ` [WIP/RFC 04/13] notes.h/c: Propagate combine_notes_fn return value to add_note() and beyond Johan Herland
2010-07-23 15:23 ` Jonathan Nieder
2010-07-23 22:39 ` Johan Herland
2010-07-23 10:14 ` [WIP/RFC 05/13] (trivial) t3303: Indent with tabs instead of spaces for consistency Johan Herland
2010-07-23 10:14 ` [WIP/RFC 06/13] notes.c: Use two newlines (instead of one) when concatenating notes Johan Herland
2010-07-23 10:14 ` [WIP/RFC 07/13] (trivial) git notes prune: Accept --verbose in addition to -v Johan Herland
2010-07-23 10:14 ` [WIP/RFC 08/13] builtin/notes.c: Split notes ref DWIMmery into a separate function Johan Herland
2010-07-23 10:15 ` [WIP/RFC 09/13] git notes merge: Initial implementation handling trivial merges only Johan Herland
2010-07-24 8:32 ` Stephen Boyd
2010-07-25 14:14 ` Johan Herland
2010-07-23 10:15 ` [WIP/RFC 10/13] builtin/notes.c: Refactor creation of notes commits Johan Herland
2010-07-23 10:15 ` [WIP/RFC 11/13] git notes merge: Handle real, non-conflicting notes merges Johan Herland
2010-07-23 10:15 ` [WIP/RFC 12/13] git notes merge: Add automatic conflict resolvers (ours, theirs, union) Johan Herland
2010-07-24 8:18 ` Stephen Boyd
2010-07-25 18:58 ` Johan Herland
2010-07-23 10:15 ` [WIP/RFC 13/13] Documentation: Preliminary docs on 'git notes merge' Johan Herland
2010-07-24 8:21 ` Stephen Boyd
2010-07-25 19:02 ` Johan Herland [this message]
2010-07-25 10:45 ` [WIP/RFC 00/13] git notes merge Sam Vilain
2010-07-25 16:44 ` 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=201007252102.52632.johan@herland.net \
--to=johan@herland.net \
--cc=bebarino@gmail.com \
--cc=git@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).