From: Peter Baumann <waste.manager@gmx.de>
To: Michal Vitecek <fuf@mageo.cz>
Cc: git list <git@vger.kernel.org>
Subject: Re: [RFH] how to know if a cherry-picked patch has been applied already?
Date: Fri, 11 Jan 2008 13:14:00 +0100 [thread overview]
Message-ID: <20080111121400.GD21695@xp.machine.xx> (raw)
In-Reply-To: <20080111104737.GA7332@mageo.cz>
On Fri, Jan 11, 2008 at 11:47:37AM +0100, Michal Vitecek wrote:
> Hello everyone,
>
> I'm managing a git repository where I include my and my co-workers'
> work. With some co-workers I can use 'git merge' but with some I use
> 'git cherry-pick'. However, cherry-picking leads to problems because a
> new commit ID is generated and I must remember which patches I have
> cherry-picked to my tree. Is there any easy way to tell which patches
> have and have not been applied?
>
> Thanks,
> Michal
Have a look at the manpage of git-cherry, which will tell you if you
already applied a commit/patch.
-Peter
prev parent reply other threads:[~2008-01-11 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 10:47 [RFH] how to know if a cherry-picked patch has been applied already? Michal Vitecek
2008-01-11 12:12 ` Johannes Schindelin
2008-01-11 12:14 ` Peter Baumann [this message]
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=20080111121400.GD21695@xp.machine.xx \
--to=waste.manager@gmx.de \
--cc=fuf@mageo.cz \
--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).