From: Johannes Sixt <j.sixt@viscovery.net>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: Support for a series of patches, i.e. patchset or changeset?
Date: Tue, 06 Nov 2012 07:39:23 +0100 [thread overview]
Message-ID: <5098B09B.7060501@viscovery.net> (raw)
In-Reply-To: <CAMPhdO-Z3E352KbTvnrxJqCecAUGfHCwOoFRUKzObh35uLnrSw@mail.gmail.com>
Am 11/6/2012 1:58, schrieb Eric Miao:
> On Mon, Nov 5, 2012 at 10:40 PM, Michael J Gruber
> <git@drmicha.warpmail.net> wrote:
>> Eric Miao venit, vidit, dixit 05.11.2012 15:12:
>>> The problem is, most cases we have no idea of the base rev1, and commit rev2
>>> which it's leading up to. E.g. for a single patch which is between
>>> commit rev1..rev2,
>>> how do we find out rev1 and rev2.
>
> E.g. when we merged a series of patches:
>
> [PATCH 00/08]
> [PATCH 01/08]
> ...
> [PATCH 08/08]
>
> How do we know this whole series after merged when only one of these
> commits are known?
You can use git name-rev. For example:
$ git name-rev 9284bdae3
9284bdae3 remotes/origin/pu~2^2~7
This tell you that the series was merged two commits before origin/pu, and
then it is the 7th from the tip of the series. Now you can
$ git log origin/pu~2^..origin/pu~2^2
to see the whole series.
-- Hannes
next prev parent reply other threads:[~2012-11-06 6:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 2:26 Support for a series of patches, i.e. patchset or changeset? Eric Miao
2012-11-05 13:39 ` Michael J Gruber
2012-11-05 14:12 ` Eric Miao
2012-11-05 14:40 ` Michael J Gruber
2012-11-06 0:58 ` Eric Miao
2012-11-06 6:39 ` Johannes Sixt [this message]
2012-11-06 6:56 ` Eric Miao
2012-11-06 7:44 ` Johannes Sixt
2012-11-07 1:50 ` Eric Miao
2012-11-08 19:09 ` Jeff King
2012-11-09 2:14 ` Eric Miao
2012-11-10 8:52 ` Enrico Weigelt
2012-11-10 9:08 ` Eric Miao
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=5098B09B.7060501@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=eric.y.miao@gmail.com \
--cc=git@drmicha.warpmail.net \
--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).