public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Luben Tuikov <ltuikov@yahoo•com>
To: git@vger•kernel.org
Subject: git-format-patch little gripe
Date: Fri, 3 Nov 2006 01:07:20 -0800 (PST)	[thread overview]
Message-ID: <376237.14965.qm@web31805.mail.mud.yahoo.com> (raw)

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.

My brain simply says:
`` "git-format-patch" is singular and so the SHA-1 specified
   on the command line should generate a _single_ patch.''

Yeah, but no.

So I still make the mistake of:
# git-rev-list --no-merges --pretty=one-line HEAD -- <somepath>
    I select a commit
# git-format-patch -o /tmp/ <commit>
...
    Oh, f@#$!  <CTRL-C>
# git-format-patch -o /tmp/ <commit>^..<commit>

Is there a chance to make "git-format-patch" output a single
patch? of that commit only?

    Luben
P.S. And let "git-format-patches" go wild with the ideologies...
Sorry, needed to vent as I made this mistake twice already
today...






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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03  9:07 Luben Tuikov [this message]
2006-11-03  9:22 ` git-format-patch little gripe Martin Langhoff
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=376237.14965.qm@web31805.mail.mud.yahoo.com \
    --to=ltuikov@yahoo$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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