git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git-commit: allow From: line to be entered in commit message
Date: Fri, 13 Jan 2006 12:46:23 -0800	[thread overview]
Message-ID: <7vvewn3lgg.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7virsn50lv.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 13 Jan 2006 12:33:48 -0800")

Junio C Hamano <junkio@cox.net> writes:

> Joel Becker <Joel.Becker@oracle.com> writes:
>
>> On Fri, Jan 13, 2006 at 11:39:17AM -0800, Junio C Hamano wrote:
>>> That's what I do.  Although I use git-am not git-applymbox, both
>>> of them are designed to work that way.
>>
>> 	While I can see that git-am and git-applymbox have different
>> options for the same basic task, I can't quite see why one would be
>> preferred to the other.  What does git-am do that git-applymbox does
>> not?

The behaviour upon seeing unapplicable patch is somewhat
different.  In Linus workflow, he reviews (and modifies if
necessary) all patches inside mbox and runs "applymbox"; upon
failure, he blows what remains in .dotest away, trims mbox to
get rid of what has already been applied and re-runs it from
scratch.  The failure recovery method "applymbox" had (this
happened before my time IIRC) is to edit .dotest/patch to make
it applicable and re-run it.  OTOH, "am" tries to do better by
allowing you to hand tweak the working tree to match what would
have resulted if the patch applied cleanly and say "--resolved".

Another difference is that "am" can be told to handle binary
file changes and apply such as long as the patch is intra
repository (i.e. both pre and post image blob are available in
the repository).  This is used as a backend to do "git rebase".

  reply	other threads:[~2006-01-13 20:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060112093700.1d3d25db.seanlkml@sympatico.ca>
2006-01-12 14:37 ` git-commit: allow From: line to be entered in commit message sean
     [not found]   ` <20060112102123.581e373e.seanlkml@sympatico.ca>
2006-01-12 15:21     ` sean
2006-01-12 20:13   ` Junio C Hamano
2006-01-12 21:53     ` Andreas Ericsson
2006-01-12 22:15       ` Junio C Hamano
     [not found]       ` <20060112214307.174f5719.seanlkml@sympatico.ca>
2006-01-13  2:43         ` sean
     [not found]     ` <20060112213207.05d76b28.seanlkml@sympatico.ca>
2006-01-13  2:32       ` sean
2006-01-13  4:03         ` Junio C Hamano
     [not found]           ` <20060112230633.0858694a.seanlkml@sympatico.ca>
2006-01-13  4:06             ` sean
2006-01-13  4:35               ` Junio C Hamano
     [not found]                 ` <20060112235103.42665813.seanlkml@sympatico.ca>
2006-01-13  4:51                   ` sean
2006-01-13 11:11                     ` Artem Khodush
2006-01-13 17:40                       ` Junio C Hamano
     [not found]                         ` <20060113125404.58c4ce30.seanlkml@sympatico.ca>
2006-01-13 17:54                           ` sean
2006-01-13 19:51                             ` Junio C Hamano
2006-01-13 21:53                               ` Johannes Schindelin
2006-01-12 19:00 ` Joel Becker
2006-01-12 20:22   ` Junio C Hamano
2006-01-13  6:58     ` Joel Becker
2006-01-13  7:06       ` Junio C Hamano
2006-01-13 19:12         ` Joel Becker
2006-01-13 19:39           ` Junio C Hamano
2006-01-13 20:01             ` Joel Becker
2006-01-13 20:33               ` Junio C Hamano
2006-01-13 20:46                 ` Junio C Hamano [this message]
2006-01-13 21:47           ` Johannes Schindelin
2006-01-12 20:16 ` Alex Riesen
     [not found]   ` <20060112214642.3c88282c.seanlkml@sympatico.ca>
2006-01-13  2:46     ` sean
2006-01-13  3:58       ` Junio C Hamano
     [not found]         ` <20060112225800.411a04c1.seanlkml@sympatico.ca>
2006-01-13  3:58           ` sean

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=7vvewn3lgg.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --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).