On Mon, Apr 14, 2014 at 12:47:11PM -0400, Martin Gagnon wrote:
Le 14 avr. 2014 11:48, Stephan Beal sgb...@googlemail.com a écrit :
But, in my defense, (and I just re-read it to be sure I didn't miss
it) nowhere in the help documentation (FOSSIL HELP COMMIT) or the
comment in the editor (#
That sounds like a bad idea to me. IMO, this is a case of good enough
getting in the way of good as far as solutions to your annoyance.
Off the top of my head, I can think of two workflow habits that may help
you:
1) set up/turn on gpg signing, so you'll be required to sign commits before
I often have the same problem for a different reason. I type “f cha” and “f
com” so often that sometime instead of “f cha” I accidentally type “f com”.
What I would like to have is an extra prompt, “Are you sure (y/N)?” with No
default for commits. Since commits are irreversible, I think the
with # are
ignored.) does it say, or even imply, that an empty comment is one of the
reasons that will 'abort' the commit.
LOL!!!
Thanks.
-Original Message-
From: Martin Gagnon
Sent: Monday, April 14, 2014 3:24 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Suggestion about fossil
On Mon, Apr 14, 2014 at 3:39 PM, Tony Papadimitriou to...@acm.org wrote:
But, in my defense, (and I just re-read it to be sure I didn't miss it)
nowhere in the help documentation (FOSSIL HELP COMMIT) or the comment in
the editor (# Enter commit message for this check-in. Lines beginning with
Le 14 avr. 2014 11:48, Stephan Beal sgb...@googlemail.com a écrit :
On Mon, Apr 14, 2014 at 3:39 PM, Tony Papadimitriou to...@acm.org wrote:
But, in my defense, (and I just re-read it to be sure I didn't miss it)
nowhere in the help documentation (FOSSIL HELP COMMIT) or the comment in
the
On 4/14/14, Martin Gagnon eme...@gmail.com wrote:
Le 14 avr. 2014 11:48, Stephan Beal sgb...@googlemail.com a écrit :
On Mon, Apr 14, 2014 at 3:39 PM, Tony Papadimitriou to...@acm.org
wrote:
But, in my defense, (and I just re-read it to be sure I didn't miss it)
nowhere in the help
On 4/14/14, 9:31 PM, B Harder wrote:
[...]
Our users shouldn't need CVS, SVN, etc experience to know this. I
added documentation to clarify.
It might also be useful to add:
# (To abort the commit, leave this file unchanged)
...to the commit message, too.
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─
On 4/14/14, David Given d...@cowlark.com wrote:
On 4/14/14, 9:31 PM, B Harder wrote:
[...]
Our users shouldn't need CVS, SVN, etc experience to know this. I
added documentation to clarify.
It might also be useful to add:
# (To abort the commit, leave this file unchanged)
...to the commit
Thus said David Given on Mon, 14 Apr 2014 22:28:07 +0100:
It might also be useful to add:
# (To abort the commit, leave this file unchanged)
I was about to point out that this wouldn't be a good idea when using
merge --cherrypick because it actually automatically includes the
Thus said Andy Bradford on Mon, 14 Apr 2014 21:40:00 -0600:
... but apparently Fossil is smart enough to figure out that even with
an uncommented line in the commit message, it still treats it as an
empty message unless you alter it!
Correction, unchanged, not empty.
Andy
--
TAI64
This might better be handled with an alias or wrapper script.
#!/bin/bash
read -p You just ran fossil $@ ; are you sure? yn
case $yn in
[Yy]* ) /usr/bin/fossil $@ ;;
[Nn]* ) echo Whew! Dodged a bullet there! ;;
esac
Elaborated to suit.
- JK
On Sun, Apr 13, 2014 at 5:41 PM, Stanislav
12 matches
Mail list logo
