From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Use git-update-ref in scripts.
Date: Thu, 29 Sep 2005 08:16:12 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0509290801230.3308@g5.osdl.org> (raw)
In-Reply-To: <7vk6h1rr9l.fsf@assigned-by-dhcp.cox.net>
On Wed, 28 Sep 2005, Junio C Hamano wrote:
>
> Hmph. That sort of makes sense but to make the unconditional
> simple case really fast it should use read-tree -m -u which
> _would_ smudge if things do not go well, which implies you need
> savestate before that which would make it slower -- wouldn't it?
Yeah, we'd have to do something like this.. (untested, surprise, surprise)
NOTE! Even if you don't take this, I noticed what looks like a missing
"continue" in the "--head" case. That just can't work without it, afaik.
Not that I know what "--head" is supposed to do..
Linus
---
diff --git a/read-tree.c b/read-tree.c
--- a/read-tree.c
+++ b/read-tree.c
@@ -13,6 +13,8 @@
static int merge = 0;
static int update = 0;
static int index_only = 0;
+static int nontrivial_merge = 0;
+static int trivial_merges_only = 0;
static int head_idx = -1;
static int merge_size = 0;
@@ -275,6 +277,9 @@ static int unpack_trees(merge_fn_t fn)
if (unpack_trees_rec(posns, len, "", fn, &indpos))
return -1;
+ if (trivial_merges_only && nontrivial_merge)
+ die("Merge requires file-level merging");
+
check_updates(active_cache, active_nr);
return 0;
}
@@ -460,6 +465,8 @@ static int threeway_merge(struct cache_e
verify_uptodate(index);
}
+ nontrivial_merge = 1;
+
/* #2, #3, #4, #6, #7, #9, #11. */
count = 0;
if (!head_match || !remote_match) {
@@ -629,9 +636,15 @@ int main(int argc, char **argv)
continue;
}
+ if (!strcmp(arg, "--trivial")) {
+ trivial_merges_only = 1;
+ continue;
+ }
+
if (!strcmp(arg, "--head")) {
head_idx = stage - 1;
fn = threeway_merge;
+ continue;
}
/* "-m" stands for "merge", meaning we start in stage 1 */
next prev parent reply other threads:[~2005-09-29 15:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 18:43 Add "git-update-ref" to update the HEAD (or other) ref Linus Torvalds
2005-09-25 19:05 ` Linus Torvalds
2005-09-25 22:37 ` Junio C Hamano
2005-09-28 2:45 ` [PATCH] Use git-update-ref in scripts Junio C Hamano
2005-09-28 15:21 ` Linus Torvalds
2005-09-28 16:56 ` Junio C Hamano
2005-09-28 17:13 ` Linus Torvalds
2005-09-28 17:29 ` Junio C Hamano
2005-09-28 18:14 ` Linus Torvalds
2005-09-28 18:28 ` Junio C Hamano
2005-09-29 16:07 ` Linus Torvalds
2005-09-28 18:17 ` Junio C Hamano
2005-09-28 19:47 ` Junio C Hamano
2005-09-28 21:19 ` Fredrik Kuivinen
2005-09-29 15:16 ` Linus Torvalds [this message]
2005-09-25 23:27 ` Add "git-update-ref" to update the HEAD (or other) ref Junio C Hamano
2005-09-26 0:50 ` Linus Torvalds
2005-09-26 4:25 ` Junio C Hamano
2005-09-26 1:07 ` Linus Torvalds
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=Pine.LNX.4.58.0509290801230.3308@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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