From: Christian Couder <christian.couder@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: git <git@vger.kernel.org>
Subject: Re: git replace --graft does error checking too late
Date: Thu, 28 Mar 2019 08:35:13 +0100 [thread overview]
Message-ID: <CAP8UFD2yMOLKOdcXnPsCvAzymjLJX2A4U2DHfq1JjvZnQj9pLQ@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD111-zqa7Fhr1KnmWYAKpBN4ofqn0AvD_nP3s_WBFzLqw@mail.gmail.com>
On Wed, Mar 27, 2019 at 2:21 PM Christian Couder
<christian.couder@gmail.com> wrote:
>
> On Wed, Mar 27, 2019 at 2:11 PM Christian Couder
> <christian.couder@gmail.com> wrote:
> >
> > On Wed, Mar 27, 2019 at 11:24 AM Andreas Schwab <schwab@suse.de> wrote:
> > >
> > > When running `git replace --graft A B' where B is a non-commit (eg. a
> > > tag) it displays an error,
> >
> > Yeah, it seems that when A is a commit and B a tag I get:
> >
> > "error: object A is a tag, not a commit"
> >
> > which is wrong as A is a commit.
>
> Actually I get the above only if A is a commit but there is a tag
> pointing to it. If there is no tag pointing to it I get:
>
> error: object C is a tag, not a commit
>
> where C is the hash of the tag object B (C=$(git rev-parse B))
>
> So yeah, this is weird.
I think I understand what happens. It seems that we put the SHA-1 of
the tag in the new object we create instead of the SHA-1 of the
underlying commit and that's what generates the error message and
other issues later.
The following patch (that unfortunately Gmail is likely to muck)
should fix at least part of the issue. I will send a real patch with
tests later.
diff --git a/builtin/replace.c b/builtin/replace.c
index f5701629a8..b0a9227f9a 100644
--- a/builtin/replace.c
+++ b/builtin/replace.c
@@ -370,16 +370,19 @@ static int replace_parents(struct strbuf *buf,
int argc, const char **argv)
/* prepare new parents */
for (i = 0; i < argc; i++) {
struct object_id oid;
+ struct commit *commit;
+
if (get_oid(argv[i], &oid) < 0) {
strbuf_release(&new_parents);
return error(_("not a valid object name: '%s'"),
argv[i]);
}
- if (!lookup_commit_reference(the_repository, &oid)) {
+ commit = lookup_commit_reference(the_repository, &oid);
+ if (!commit) {
strbuf_release(&new_parents);
- return error(_("could not parse %s"), argv[i]);
+ return error(_("could not parse %s as a
commit"), argv[i]);
}
- strbuf_addf(&new_parents, "parent %s\n", oid_to_hex(&oid));
+ strbuf_addf(&new_parents, "parent %s\n",
oid_to_hex(&commit->object.oid));
}
/* replace existing parents with new ones */
prev parent reply other threads:[~2019-03-28 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 10:22 git replace --graft does error checking too late Andreas Schwab
2019-03-27 13:11 ` Christian Couder
2019-03-27 13:21 ` Christian Couder
2019-03-28 7:35 ` Christian Couder [this message]
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=CAP8UFD2yMOLKOdcXnPsCvAzymjLJX2A4U2DHfq1JjvZnQj9pLQ@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=schwab@suse.de \
/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).