All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@mellanox.co.il>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: Merge git-gui into 1.5.0 ?
Date: Mon, 12 Feb 2007 07:40:18 +0200	[thread overview]
Message-ID: <20070212054018.GC28231@mellanox.co.il> (raw)
In-Reply-To: <20070211230204.GE31488@spearce.org>

> Quoting Shawn O. Pearce <spearce@spearce.org>:
> Subject: Re: Merge git-gui into 1.5.0 ?
> 
> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > > It may make patching slightly more interesting though, as some
> > > users new to git-gui development may generate a patch in git.git
> > > (using a/git-gui/git-gui.sh as the path) which then would not apply
> > > as-is to the master git-gui development tree.
> > 
> > In this case, a "-p <n>" option to git-am would make sense, no?
> 
> Are you saying we just suddenly found a vaild use for a flag which
> nobody (except the original submitter) thought was useful?  ;-)
> 
> Yes, clearly a -p<n> on git-am would solve the problem quite nicely.

Actually, -p<n> option to git-am is also useful for piping
patches to git-am directly from mail: sometimes people would generate
a patch by hand and this results in patches incorrect -p level.
	
-- 
MST

  parent reply	other threads:[~2007-02-12  5:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-11  8:40 Merge git-gui into 1.5.0 ? Shawn O. Pearce
2007-02-11 14:57 ` Mark Levedahl
2007-02-11 22:49   ` Shawn O. Pearce
2007-02-11 16:39 ` Johannes Schindelin
2007-02-11 22:27 ` Junio C Hamano
2007-02-11 22:41   ` Shawn O. Pearce
2007-02-11 22:53     ` Johannes Schindelin
2007-02-11 23:02       ` Shawn O. Pearce
2007-02-11 23:25         ` Johannes Schindelin
2007-02-12  5:40         ` Michael S. Tsirkin [this message]
2007-02-12  5:48           ` Junio C Hamano
2007-02-12  5:59             ` Michael S. Tsirkin
2007-02-12  6:25               ` Michael S. Tsirkin
2007-02-12 11:51                 ` add negative -p to git-am, " Johannes Schindelin
2007-02-12 11:59                   ` Michael S. Tsirkin
2007-02-12 12:06                     ` Johannes Schindelin
2007-02-12 12:26                       ` Michael S. Tsirkin
2007-02-12 21:55     ` Junio C Hamano
2007-02-12 23:34       ` Shawn O. Pearce
2007-02-12 23:38       ` Johannes Schindelin
2007-02-12 23:42         ` Shawn O. Pearce
2007-02-12 23:53           ` Johannes Schindelin
2007-02-13  0:34             ` Jakub Narebski
2007-02-13  0:38               ` Shawn O. Pearce

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=20070212054018.GC28231@mellanox.co.il \
    --to=mst@mellanox.co.il \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=spearce@spearce.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 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.