From: Martin Langhoff <martin.langhoff@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: Patch (apply) vs. Pull
Date: Thu, 23 Jun 2005 20:47:03 +1200 [thread overview]
Message-ID: <46a038f9050623014755acb1c6@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0506221504370.2353@ppc970.osdl.org>
On 6/23/05, Linus Torvalds <torvalds@osdl.org> wrote:
> I've been doing unified diffs for a _loong_ time, and I edit patches in my
> sleep. The rules for line numbers etc are really quite simple, and yes, I
> do edit patches before I apply them.
We often do unified diff editing when dealing with merge conflicts. It
isn't too hard once you've got the hang of it, usually the hard thing
is resolving the conflict in the first place.
Emacs has a diff editing mode that is really good:
http://wiki.gnuarch.org/Process_20_2a_2erej_20files
cheers,
martin
next prev parent reply other threads:[~2005-06-23 8:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 16:19 Patch (apply) vs. Pull Darrin Thompson
2005-06-20 17:22 ` Junio C Hamano
2005-06-20 23:01 ` Darrin Thompson
2005-06-21 18:02 ` Daniel Barkalow
2005-06-22 8:47 ` Junio C Hamano
2005-06-22 9:56 ` Catalin Marinas
2005-06-21 22:09 ` Linus Torvalds
2005-06-22 9:08 ` Junio C Hamano
2005-06-22 17:21 ` Linus Torvalds
2005-06-22 20:08 ` Daniel Barkalow
2005-06-22 20:22 ` Linus Torvalds
2005-06-22 21:54 ` Daniel Barkalow
2005-06-22 22:21 ` Linus Torvalds
2005-06-23 3:32 ` Daniel Barkalow
2005-06-23 4:23 ` Linus Torvalds
2005-06-23 5:15 ` Daniel Barkalow
2005-06-23 6:09 ` Linus Torvalds
2005-06-23 16:45 ` Daniel Barkalow
2005-06-23 18:43 ` Linus Torvalds
2005-06-23 19:59 ` Daniel Barkalow
2005-06-23 22:20 ` Linus Torvalds
2005-06-23 22:49 ` Linus Torvalds
2005-06-23 12:10 ` Catalin Marinas
2005-06-23 17:05 ` Daniel Barkalow
2005-06-24 13:41 ` Catalin Marinas
2005-06-23 8:47 ` Martin Langhoff [this message]
2005-06-22 16:23 ` Darrin Thompson
2005-06-23 8:36 ` Martin Langhoff
2005-06-23 23:21 ` [PATCH 0/3] Rebasing for "individual developer" usage Junio C Hamano
2005-06-23 23:27 ` [PATCH 1/3] git-commit-script: get commit message from an existing one Junio C Hamano
2005-06-23 23:28 ` [PATCH 2/3] git-cherry: find commits not merged upstream Junio C Hamano
2005-06-23 23:29 ` [PATCH 3/3] git-rebase-script: rebase local commits to new upstream head Junio C Hamano
2005-06-22 17:04 ` Patch (apply) vs. Pull Catalin Marinas
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=46a038f9050623014755acb1c6@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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).