From: Christian Couder <christian.couder@gmail.com>
To: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>
Cc: git <git@vger.kernel.org>
Subject: Re: How to determine the order of commit
Date: Tue, 5 Mar 2019 13:39:00 +0100 [thread overview]
Message-ID: <CAP8UFD21SaWUSqpKjTYVQkbQxLpFEhvjJW8019i6tAS9agnWGg@mail.gmail.com> (raw)
In-Reply-To: <40f11dda.1d424.1694d0cd42b.Coremail.wuzhouhui14@mails.ucas.ac.cn>
Hi,
On Tue, Mar 5, 2019 at 10:00 AM wuzhouhui <wuzhouhui14@mails.ucas.ac.cn> wrote:
>
> Suppose I have "git format-patch" two commit from a repository like
> following:
>
> git format-patch -1 cf1c9ccba730
> git format-patch -1 d1a2930d8a99
>
> Now, how to determine the commit order of these two patch in repository?
Do you mean something like:
$ git merge-base --is-ancestor cf1c9ccba730 d1a2930d8a99
and:
$ git merge-base --is-ancestor d1a2930d8a99 cf1c9ccba730
?
next prev parent reply other threads:[~2019-03-05 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 8:51 How to determine the order of commit wuzhouhui
2019-03-05 12:39 ` Christian Couder [this message]
2019-03-05 13:17 ` wuzhouhui
2019-03-05 13:59 ` 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=CAP8UFD21SaWUSqpKjTYVQkbQxLpFEhvjJW8019i6tAS9agnWGg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=wuzhouhui14@mails.ucas.ac.cn \
/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).