git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David A. Wheeler" <dwheeler@dwheeler.com>
To: Petr Baudis <pasky@ucw.cz>
Cc: Ingo Molnar <mingo@elte.hu>, git@vger.kernel.org
Subject: Re: [script] ge: export commits as patches
Date: Tue, 19 Apr 2005 22:34:43 -0400	[thread overview]
Message-ID: <4265BFC3.9080105@dwheeler.com> (raw)
In-Reply-To: <20050419194108.GN12757@pasky.ji.cz>

Forget my earlier "aspatch" proposal, that's a lousy name.

How about "mkpatch"?  Seems like a reasonable name for
a command that makes a patch.  GNU Arch uses that command name.
CVS & Subversion basically do this as part of "diff"
(which is another possibility).

--- David A. Wheeler

  reply	other threads:[~2005-04-20  2:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 13:48 [script] ge: export commits as patches Ingo Molnar
2005-04-19 17:03 ` Petr Baudis
2005-04-19 18:56   ` Ingo Molnar
2005-04-19 19:41     ` Petr Baudis
2005-04-20  2:34       ` David A. Wheeler [this message]
2005-04-19 19:11   ` Greg KH
2005-04-19 22:56   ` David A. Wheeler
2005-04-20 17:21 ` Zlatko Calusic

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=4265BFC3.9080105@dwheeler.com \
    --to=dwheeler@dwheeler.com \
    --cc=git@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pasky@ucw.cz \
    /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).