From: Alex Riesen <raa.lkml@gmail.com>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: git@vger.kernel.org
Subject: Re: cherry-pick --since ?
Date: Fri, 20 Apr 2007 20:55:24 +0200 [thread overview]
Message-ID: <20070420185524.GA4420@steel.home> (raw)
In-Reply-To: <Pine.LNX.4.64.0704201100050.4667@torch.nrlssc.navy.mil>
Brandon Casey, Fri, Apr 20, 2007 18:20:32 +0200:
> Is there functionality to allow something akin to a
>
> git cherry-pick --since <commit>
>
git format-patch --stdin --binary --full-index -k from..to | git am -k -3
next prev parent reply other threads:[~2007-04-20 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 16:20 cherry-pick --since ? Brandon Casey
2007-04-20 18:55 ` Alex Riesen [this message]
2007-04-22 12:06 ` David Kågedal
2007-04-20 23:05 ` Junio C Hamano
2007-04-23 17:52 ` Brandon Casey
2007-04-23 19:32 ` Junio C Hamano
2007-04-23 23:18 ` Brandon Casey
2009-07-16 8:11 ` Git range merge (cherry-pick a range) bshOriginal
2009-07-16 11:36 ` Michael J Gruber
[not found] ` <6efe9a9b0907160516o75641919wd1eecf5229aea895@mail.gmail.com>
2009-07-16 12:44 ` Michael J Gruber
2009-07-16 16:27 ` Daniel Barkalow
2009-07-17 8:41 ` bshOriginal
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=20070420185524.GA4420@steel.home \
--to=raa.lkml@gmail.com \
--cc=casey@nrlssc.navy.mil \
--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).