git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: ltuikov@yahoo.com
Cc: git@vger.kernel.org
Subject: Re: git-format-patch little gripe
Date: Fri, 3 Nov 2006 22:22:21 +1300	[thread overview]
Message-ID: <46a038f90611030122reecee87ufac5bbaa910ee933@mail.gmail.com> (raw)
In-Reply-To: <376237.14965.qm@web31805.mail.mud.yahoo.com>

On 11/3/06, Luben Tuikov <ltuikov@yahoo.com> wrote:
> Yep, after more than a year, I simply cannot get used to it...
> http://marc.theaimsgroup.com/?l=git&m=113259043217761&w=2
> And as I've seen, other people brought that up too.

Hi Luben,

reading the thread, it sounds like you have a couple of shells scripts
or aliases that do what you want already ;-)

And for the scenario you mention, where upstream has taken some of
your patches... git-format-patch automatically tries to skip those.
Works well for me at least (ducks).



  reply	other threads:[~2006-11-03  9:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03  9:07 git-format-patch little gripe Luben Tuikov
2006-11-03  9:22 ` Martin Langhoff [this message]
2006-11-03  9:59   ` Luben Tuikov
2006-11-03 11:17     ` Junio C Hamano
2006-11-03 17:32       ` Carl Worth
2006-11-03 17:51         ` Jakub Narebski
2006-11-03 19:52       ` Luben Tuikov
2006-11-03 20:53         ` Jakub Narebski
2006-11-03 22:26         ` Junio C Hamano
2006-11-03 22:35           ` Carl Worth
2006-11-03 23:16             ` Jeff King
2006-11-03 23:37               ` Jakub Narebski
2006-11-04  0:44                 ` Linus Torvalds
2006-11-04  1:05                   ` Jakub Narebski
2006-11-03 18:50 ` Jeff King
2006-11-03 20:37   ` Luben Tuikov
2006-11-25 15:30   ` Sean
     [not found]   ` <20061125103033.2ea742d3.seanlkml@sympatico.ca>
2006-11-25 15:39     ` Jeff King
2006-11-25 15:42       ` 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=46a038f90611030122reecee87ufac5bbaa910ee933@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ltuikov@yahoo.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).