From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Junio C Hamano" <gitster@pobox.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
git@vger.kernel.org, quilt-dev@nongnu.org
Subject: Re: being nice to patch(1)
Date: Tue, 3 Jul 2007 14:21:51 +0200 [thread overview]
Message-ID: <4d8e3fd30707030521k6cb3129dy9193344e9e1eccf7@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707031303130.4071@racer.site>
On 7/3/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
> On Mon, 2 Jul 2007, Linus Torvalds wrote:
> > On Mon, 2 Jul 2007, Junio C Hamano wrote:
> > > Linus Torvalds <torvalds@linux-foundation.org> writes:
> > >
> > > > So I would suggest that in quilt and other systems, you either:
> > > >
> > > > - strip all headers manually
> > > >
> > > > - forget about "patch", and use "git-apply" instead that does things
> > > > right and doesn't screw up like this (and can do rename diffs etc too).
> > > >
> > > > I guess the second choice generally isn't an option, but dammit,
> > > > "git-apply" really is the better program here.
> > >
> > > Why not? git-apply works outside of a git repo ;-)
> >
> > I was more thinking that people are not necessarily willing to install git
> > just to get the "git-apply" program..
>
> But maybe they would be willing to install git to get that wonderful
> git-apply program, and that wonderful rename-and-mode-aware git-diff, and
> the git-merge-file program, all of which can operate outside of a git
> repository. (Take that, hg!)
How about shipping just these commands as a separate package?
Is that a cray idea?
ciao,
--
Paolo
"Tutto cio' che merita di essere fatto,merita di essere fatto bene"
Philip Stanhope IV conte di Chesterfield
next prev parent reply other threads:[~2007-07-03 12:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 19:54 being nice to patch(1) Andrew Morton
2007-07-02 21:16 ` Linus Torvalds
2007-07-02 21:25 ` Andrew Morton
2007-07-02 21:40 ` Linus Torvalds
2007-07-02 21:56 ` Andrew Morton
2007-07-03 0:28 ` Linus Torvalds
2007-07-03 4:00 ` Junio C Hamano
2007-07-03 4:14 ` Linus Torvalds
2007-07-03 12:04 ` Johannes Schindelin
2007-07-03 12:21 ` Paolo Ciarrocchi [this message]
2007-07-03 12:35 ` Johannes Schindelin
2007-07-03 18:39 ` Theodore Tso
2007-07-03 19:48 ` Linus Torvalds
2007-07-03 20:55 ` Paul Eggert
2007-07-03 21:30 ` Linus Torvalds
2007-07-03 21:35 ` Linus Torvalds
2007-07-03 13:22 ` David Kastrup
2007-07-03 13:39 ` Johannes Schindelin
2007-07-03 13:54 ` David Kastrup
2007-07-03 15:01 ` [PATCH] diff --no-index: fix --name-status with added files Johannes Schindelin
2007-07-03 15:01 ` being nice to patch(1) Johannes Schindelin
2007-07-03 15:08 ` David Kastrup
2007-07-06 12:38 ` David Kastrup
2007-07-06 15:22 ` git-diff memory/speed/disk impacts (was: being nice to patch(1)) David Kastrup
2007-07-06 18:08 ` being nice to patch(1) Linus Torvalds
2007-07-03 13:34 ` [Quilt-dev] " Andreas Gruenbacher
2007-07-03 15:49 ` Andrew Morton
2007-07-03 16:03 ` Linus Torvalds
2007-07-03 16:03 ` Andreas Gruenbacher
2007-07-03 16:15 ` Andrew Morton
2007-07-03 21:03 ` Andrew Morton
2007-07-03 21:03 ` Andrew Morton
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=4d8e3fd30707030521k6cb3129dy9193344e9e1eccf7@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=quilt-dev@nongnu.org \
--cc=torvalds@linux-foundation.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).