From: Timur Tabi <timur@freescale.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Sean Kelley <svk.sweng@gmail.com>, git@vger.kernel.org
Subject: Re: git-apply versus git-am
Date: Mon, 23 Jul 2007 12:20:40 -0500 [thread overview]
Message-ID: <46A4E368.7080909@freescale.com> (raw)
In-Reply-To: <7vsl7flctg.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> applymbox is going away.
That sucks! I like git-am. Is there a replacement command that applies a patch and
commits it at the same time? If I use git-apply on a patch that adds new files, I need to
use git-add on the files before I can commit it. That's a real pain.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-07-23 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 7:54 git-apply versus git-am Sean Kelley
2007-07-23 8:31 ` Alex Riesen
2007-07-23 8:54 ` Junio C Hamano
2007-07-23 17:20 ` Timur Tabi [this message]
2007-07-23 17:34 ` Johannes Schindelin
2007-07-23 17:37 ` Timur Tabi
2007-07-23 17:37 ` Peter Baumann
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=46A4E368.7080909@freescale.com \
--to=timur@freescale.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=svk.sweng@gmail.com \
/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).