From: "Michael S. Tsirkin" <mst@mellanox.co.il>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] add -C[NUM] to git-am
Date: Wed, 7 Feb 2007 23:19:10 +0200 [thread overview]
Message-ID: <20070207211910.GK12140@mellanox.co.il> (raw)
In-Reply-To: <7vejp17m3t.fsf@assigned-by-dhcp.cox.net>
> Quoting r. Junio C Hamano <junkio@cox.net>:
> Subject: Re: [PATCH] add -C[NUM] to git-am
>
> "Michael S. Tsirkin" <mst@mellanox.co.il> writes:
>
> > Add -C[NUM] to git-am so that patches can be applied even
> > if context has changed a bit.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@mellanox.co.il>
> >
> > ---
> >
> > I just had to apply a largish number of patches on a project
> > that has evolved since, and I found the following to be useful.
> >
> > What do others think.
>
> FWIW, I am in favor although I do not foresee myself ever using
> it. However, this has slight ramifications.
>
> - we will be keeping applymbox after all. shouldn't this be
> side-ported to it?
OK.
> - am is used as a workhorse for rebase. shouldn't this be
> accessible through its command line as well?
How will it be used?
--
MST
next prev parent reply other threads:[~2007-02-07 21:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 20:15 [PATCH] add -C[NUM] to git-am Michael S. Tsirkin
2007-02-07 20:23 ` Junio C Hamano
2007-02-07 21:19 ` Michael S. Tsirkin [this message]
2007-02-08 7:52 ` Junio C Hamano
2007-02-08 8:35 ` Jakub Narebski
2007-02-08 13:57 ` Michael S. Tsirkin
2007-02-08 23:04 ` Junio C Hamano
2007-02-07 23:50 ` Johannes Schindelin
2007-02-07 23:54 ` Jakub Narebski
2007-02-08 0:07 ` Johannes Schindelin
2007-02-08 0:17 ` 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=20070207211910.GK12140@mellanox.co.il \
--to=mst@mellanox.co.il \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.