From: Junio C Hamano <gitster@pobox.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: git@vger.kernel.org, nicolas.dichtel@6wind.com,
Jeff King <peff@peff.net>
Subject: Re: [PATCH] revert.c: defer writing CHERRY_PICK_HEAD till it is safe to do so
Date: Thu, 06 Oct 2011 10:28:22 -0700 [thread overview]
Message-ID: <7vaa9e113d.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAG+J_Dzh2Njjwykt-f4w_YqpftrJEpQfUW2OvSRs_MSPcNFQnw@mail.gmail.com> (Jay Soffian's message of "Thu, 6 Oct 2011 13:21:40 -0400")
Jay Soffian <jaysoffian@gmail.com> writes:
> For that matter, why does revert.c have it's own implementation of
> recursive instead of just calling try_merge_command("recursive", ...)?
I think the people who did this part wanted not to fork.
next prev parent reply other threads:[~2011-10-06 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 14:34 [PATCH] revert.c: defer writing CHERRY_PICK_HEAD till it is safe to do so Jay Soffian
2011-10-06 17:02 ` Junio C Hamano
2011-10-06 17:21 ` Jay Soffian
2011-10-06 17:28 ` Junio C Hamano [this message]
2011-10-06 17:28 ` Jay Soffian
2011-10-06 17:33 ` Jay Soffian
2011-10-06 21:49 ` Junio C Hamano
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=7vaa9e113d.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=nicolas.dichtel@6wind.com \
--cc=peff@peff.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;
as well as URLs for NNTP newsgroup(s).