git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Support for a series of patches, i.e. patchset or changeset?
Date: Mon, 05 Nov 2012 14:39:28 +0100	[thread overview]
Message-ID: <5097C190.80406@drmicha.warpmail.net> (raw)
In-Reply-To: <CAMPhdO_33CPJv2hAvPuJ10KZ7v_fgP9P2kV_WLVK2tapjQQ5=A@mail.gmail.com>

Eric Miao venit, vidit, dixit 05.11.2012 03:26:
> Hi All,
> 
> Does anyone know if git has sort of support for a series of patches, i.e.
> a patchset or changeset? So whenever we know the SHA1 id of a single
> patch/commit, we know the patchset it belongs to. This is normal when
> we do big changes and split that into smaller pieces and doing only one
> simple thing in a single commit.
> 
> This will be especially useful when tracking and cherry-picking changes,
> i.e. monitoring on the changes of some specific files, and if a specific
> patch is interesting, we may want to apply the whole changeset, not only
> that specific one.

First of all, if you know the sha1 of a commit, then all its ancestors
are determined by that. If you want to describe a set of patches, say
based on rev1 and leading up to rev2, then the expression

rev2 ^rev1

describes that set uniquely. Often you can do without ^rev1, e.g. if you
know that all patch series are developed bases on origin/master, then
specifying rev2 is enough as "git rev-list rev2 ^origin/master" will
give you all commits in the series (unless they have been integrated,
i.e. merged).

Or are you thinking about patches "independent" of a base?

Cheers,
Michael

  reply	other threads:[~2012-11-05 13: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 [this message]
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
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=5097C190.80406@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=eric.y.miao@gmail.com \
    --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).