git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: git@vger.kernel.org
Subject: Re: Per-file, possibly even per-hunk cherry picking
Date: Wed, 11 Jul 2007 00:48:15 +1200	[thread overview]
Message-ID: <4693800F.4010308@vilain.net> (raw)
In-Reply-To: <469378AB.7030909@vilain.net>

Sam Vilain wrote:
> I'm interested in extending the cherry analysis to allow specification
> of the diff options used when calculating diff IDs, presenting the
> calculated diff IDs for analysis by external tools, and even calculating
> and dealing with per-hunk diff IDs.
>   

On reflection I think so long as --cherry-pick works together with a
file selection, it would probably be enough.

ie, if I have these commits:

A---B
 \
  \
   C

B changes a file foo.c, adding a line of text.  C changes foo.c as well
as bar.c, but the change in foo.c was identical to change B.

I want this to show me nothing:

  git-rev-list --left-right --cherry-pick B...C -- foo.c

Would it be the right approach to put this information in ids->diffopts,
or somewhere else?

Sam.

  reply	other threads:[~2007-07-10 12:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 12:16 Per-file, possibly even per-hunk cherry picking Sam Vilain
2007-07-10 12:48 ` Sam Vilain [this message]
2007-07-10 13:50   ` [PATCH] Fix --cherry-pick with given paths Johannes Schindelin
2007-07-10 14:22     ` Sam Vilain
2007-07-11 22:00     ` 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=4693800F.4010308@vilain.net \
    --to=sam@vilain.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).