From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: support for git commit --amend/--signoff
Date: Sat, 26 Jun 2010 12:11:55 +0200 [thread overview]
Message-ID: <87y6e2xfv8.fsf@lola.goethe.zz> (raw)
In-Reply-To: buo7hlnibft.fsf@dhlpc061.dev.necel.com
Miles Bader <miles@gnu.org> writes:
> Dan Nicolaescu <dann@gnu.org> writes:
>> Given that you don't really plan to do anything about it, and I am
>> convinced that it's the wrong solution for the problem based on my
>> personal experience both with this particular feature and from using
>> perforce.
>
> I kinda like Stefan's method better too.
It seems like it would be quite more problematic to script/macro/batch.
Perhaps one needs to think about an argument for non-interactive use
that makes it easy to substitute for the editing of the commit message?
So if one pre-specifies command line options in some manner, the
respective pseudo-lines in the commit message are not generated in the
first place?
That way, one can use Stefan's method by default, but rather
transparently move to as much of Dan's method as one likes.
Anyway, the principal problem appears similar to web forums as opposed
to Usenet. They seem user-friendly on the surface, but I can't keep up
with more than a few web forums because of time restraints. Handling
dozens of Usenet groups via gnus, in contrast, is easy.
--
David Kastrup
next prev parent reply other threads:[~2010-06-26 10:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 6:19 support for git commit --amend/--signoff Dan Nicolaescu
2010-06-11 8:09 ` Juri Linkov
2010-06-11 13:23 ` Dan Nicolaescu
2010-06-11 14:18 ` Stefan Monnier
2010-06-11 16:14 ` Štěpán Němec
2010-06-11 20:26 ` Stefan Monnier
2010-06-12 2:19 ` Dan Nicolaescu
2010-06-12 19:59 ` Juri Linkov
2010-06-12 20:19 ` Stefan Monnier
2010-06-19 6:38 ` Dan Nicolaescu
2010-06-23 7:17 ` Stefan Monnier
2010-06-23 7:45 ` David Kastrup
2010-06-23 9:00 ` Miles Bader
2010-06-23 18:55 ` Dan Nicolaescu
2010-06-23 18:45 ` Dan Nicolaescu
2010-06-23 22:04 ` Stefan Monnier
2010-06-23 23:23 ` Dan Nicolaescu
2010-06-24 21:03 ` Stefan Monnier
2010-06-24 21:18 ` Dan Nicolaescu
2010-06-24 22:25 ` Stefan Monnier
2010-06-24 23:14 ` Dan Nicolaescu
2010-06-25 1:16 ` Stefan Monnier
2010-06-25 2:27 ` Dan Nicolaescu
2010-06-25 11:44 ` Miles Bader
2010-06-26 5:09 ` Dan Nicolaescu
2010-07-01 0:01 ` Stefan Monnier
2010-06-26 10:11 ` David Kastrup [this message]
2010-06-28 21:04 ` Juri Linkov
2010-06-11 17:34 ` Dan Nicolaescu
2010-06-11 19:27 ` Juri Linkov
2010-06-11 20:16 ` Dan Nicolaescu
2010-06-11 20:38 ` Juri Linkov
2010-06-11 23:48 ` W Dan Meyer
2010-06-12 20:23 ` Juri Linkov
2010-06-12 2:21 ` Dan Nicolaescu
2010-06-11 23:44 ` Thien-Thi Nguyen
2010-06-12 20:15 ` Stefan Monnier
2010-06-11 20:35 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y6e2xfv8.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).