From: "Sitaram Chamarty" <sitaramc@gmail.com>
To: git@vger.kernel.org
Subject: Re: two git-cherry-pick enhancements
Date: Thu, 22 May 2008 14:28:49 +0530 [thread overview]
Message-ID: <2e24e5b90805220158n5c31da1yf98cac8b432a2d9d@mail.gmail.com> (raw)
In-Reply-To: <20080521163817.GA13124@denkbrett.schottelius.org>
On Wed, May 21, 2008 at 10:08 PM, Nico -telmich- Schottelius
<nico-git-20080521@schottelius.org> wrote:
> - Apply only parts of the patch which applies to <file ...>:
> I sometimes want to apply patches only to some, but not all
> files the patch introduces
>
> - Interactively selecting which parts to apply:
> I want only 7 out of 10 changes the patch introduces.
> It would help alot, if I could choose which parts I want
> to apply for every part of the patch.
Both of these are (often, though not always) signs that commits are
not granular enough. Your branch maintainer or developer has combined
unrelated things into one commit. In an ideal world, he would put
each piece as a separate commit, such that if you pick one of those
apart, it doesn't make sense.
This is also usually a sign of someone using a central VCS model (or
mental model) on that side.
Unless you have no control over who sends you these commits, you may
want to address that also in whatever way possible.
IMO stuff like "git add -a" (and the GUI equivalents) were meant for
your own development, so that you can essentially re-write history in
a sane sequence after having worked on a complex task.
Regards,
Sitaram
next prev parent reply other threads:[~2008-05-22 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 16:38 two git-cherry-pick enhancements Nico -telmich- Schottelius
2008-05-21 18:36 ` Govind Salinas
2008-05-22 8:58 ` Sitaram Chamarty [this message]
2008-05-22 9:29 ` Johannes Schindelin
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=2e24e5b90805220158n5c31da1yf98cac8b432a2d9d@mail.gmail.com \
--to=sitaramc@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).