From: Nikolaj Schumacher <n_schumacher@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Alexandre Julliard <julliard@winehq.org>
Subject: Re: [PATCH v2/RFC] git.el: Commands for committing patches
Date: Tue, 24 Jun 2008 22:44:56 +0200 [thread overview]
Message-ID: <m2r6amtvef.fsf@nschum.de> (raw)
In-Reply-To: <7vlk0vhmeb.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Mon\, 23 Jun 2008 14\:27\:56 -0700")
Junio C Hamano <gitster@pobox.com> wrote:
> I do not use things in contrib/emacs/git.el myself, but this looks like a
> lot of code to do what "M-| git am <Enter>" already does...
I admit committing email buffers might be unnecessary. I consider it
more of a cherry-on-top. The important part is committing patches,
because it gives way to partial commits (below file level).
regards,
Nikolaj Schumacher
prev parent reply other threads:[~2008-06-24 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 23:35 [PATCH/RFC] git.el: Commands for committing patches Nikolaj Schumacher
2008-06-23 1:59 ` Edward Z. Yang
2008-06-23 7:25 ` Nikolaj Schumacher
2008-06-23 7:41 ` [PATCH v2/RFC] " Nikolaj Schumacher
2008-06-23 21:27 ` Junio C Hamano
2008-06-24 20:44 ` Nikolaj Schumacher [this message]
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=m2r6amtvef.fsf@nschum.de \
--to=n_schumacher@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=julliard@winehq.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.