On Wed, Jul 22, 2015 at 12:10 AM, Andy Bradford amb-fos...@bradfords.org
wrote:
Also, I just realized, while there is no limit in the manifest design,
nor is there a limit elsewhere internal, does this mean that the Fossil
CLI has to allow someone to submit more than a fixed number? If
Thus said Stephan Beal on Tue, 21 Jul 2015 09:28:43 +0200:
To be honest, i wouldn't bother with this - the code overhead of
having to collect and sort the tags would not be worth it for this
case, IMO. In principle there is no inherent limit. Save it for v2 ;).
Also, I just
Thus said Stephan Beal on Tue, 21 Jul 2015 09:28:43 +0200:
for bonus points (certainly not necessary), allow multiple
f-tag/-cancel lags:
An unlimited of them (except of course by memory)? Or Fossil only
account for a maximum number of tags? If the latter, what?
To be
On Tue, Jul 21, 2015 at 7:07 AM, Andy Bradford amb-fos...@bradfords.org
wrote:
Thus said Stephan Beal on Thu, 16 Jul 2015 08:19:00 +0200:
for bonus points (certainly not necessary), allow multiple
f-tag/-cancel lags:
An unlimited of them (except of course by memory)? Or
Thus said Stephan Beal on Thu, 16 Jul 2015 08:19:00 +0200:
for bonus points (certainly not necessary), allow multiple
f-tag/-cancel lags:
An unlimited of them (except of course by memory)? Or Fossil only
account for a maximum number of tags? If the latter, what?
Thanks,
On Sat, 18 Jul 2015, Andy Bradford wrote:
Thus said Sergei Gavrikov on Sat, 18 Jul 2015 12:10:42 +0300:
However, with a forest the options Fossil CLI increasingly resembles
Git CLI :-)
Perhaps then, ``amend'' should only have short options where ``commit''
has short options?
I think
On Sat, 18 Jul 2015, Scott Robison wrote:
Still on phone. Instead of -euser how about -author? Instinctively seems
less clumsy but it's just a knee-jerk reaction to -euser which seems both
long and short simultaneously. :)
+1
I would vote for `-author' or for any not abbreviated word(s).
On Sat, 17 Jul 2015, Andy Bradford wrote:
Thus said Sergei Gavrikov on Thu, 16 Jul 2015 17:21:55 +0300:
I also expected that 'fossil amend uuid' will spawn $EDITOR with an
original check-in message likes 'fossil commit' does. But, I met cold
silence. Probably, to support $EDITOR for
On Sat, Jul 18, 2015 at 4:37 AM, Andy Bradford amb-fos...@bradfords.org
wrote:
Also, should some of these options have a short option analog, for
example:
-u|--euser USER Make USER the check-in user
Why is 'e'user needed? Is there a global flag for --user which collides
Thus said Stephan Beal on Sat, 18 Jul 2015 09:46:40 +0200:
Why is 'e'user needed? Is there a global flag for --user which
collides with it?
Yes, unfortunately there is the global --user option with which it
collides. Setting it causes Fossil to fail with an error about not being
Thus said Sergei Gavrikov on Sat, 18 Jul 2015 15:18:09 +0300:
Back to amend's options. Short counter-part for `--comment' option
would be `-m' option. The fossil commit command uses `-m'.
Yes, much better suggestion, thank you. I'll take a look at the commit
command and see how many
On Sat, Jul 18, 2015 at 4:29 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
It doesn't have to be euser, but the rational there was for edited user.
Have another suggestion?
No better suggestion - euser matches the event table, too.
-s|--close
just so that the short-form flag is a
Thus said Stephan Beal on Sat, 18 Jul 2015 16:35:46 +0200:
-e|--edit-comment Launch editor to revise comment
i know my own most-used will be -e, but i like -m (as mentioned
earlier) for this: -m|-comment for symmetry with commit. #2 would be
tagging, #3 would be the two
On 18/07/15 17:09, Scott Robison wrote:
Still on phone. Instead of -euser how about -author? Instinctively seems
less clumsy but it's just a knee-jerk reaction to -euser which seems both
long and short simultaneously. :)
I agree x 2.
--
Kind Regards,
Jan
Thus said Scott Robison on Fri, 17 Jul 2015 22:20:35 -0600:
On phone, apologies for top posting. To me amend uuid should
behave as much as possible like commit, though I can appreciate that
some might disagree.
Is the primary purpose, or most frequent use, of the amend subcommand to
On 18 July 2015 at 11:54, Stephan Beal sgb...@googlemail.com wrote:
On Sat, Jul 18, 2015 at 11:10 AM, Sergei Gavrikov
sergei.gavri...@gmail.com wrote:
--edit-comment option. However, with a forest the options Fossil CLI
increasingly resembles Git CLI :-)
See:
On Sat, 18 Jul 2015, Stephan Beal wrote:
On Sat, Jul 18, 2015 at 11:10 AM, Sergei Gavrikov wrote:
--edit-comment option. However, with a forest the options Fossil
CLI increasingly resembles Git CLI :-)
See:
http://git-man-page-generator.lokaltog.net/
Of course, I have been
On Sat, Jul 18, 2015 at 11:10 AM, Sergei Gavrikov sergei.gavri...@gmail.com
wrote:
--edit-comment option. However, with a forest the options Fossil CLI
increasingly resembles Git CLI :-)
See:
http://git-man-page-generator.lokaltog.net/
--
- stephan beal
Thus said Stephan Beal on Fri, 17 Jul 2015 06:55:29 +0200:
Or maybe it's just me!
I disagree, I don't think it's you at all. Filtering problems are always
due to faulty design or bad heuristics. If I filter email (or gmail in
this case) that happens to be legitimate email, regardless of
On Fri, Jul 17, 2015 at 4:49 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
Thus said Stephan Beal on Fri, 17 Jul 2015 06:55:29 +0200:
Or maybe it's just me!
I disagree, I don't think it's you at all. Filtering problems are always
due to faulty design or bad heuristics. If I filter
Thus said Sergei Gavrikov on Thu, 16 Jul 2015 17:21:55 +0300:
I also expected that 'fossil amend uuid' will spawn $EDITOR with an
original check-in message likes 'fossil commit' does. But, I met cold
silence. Probably, to support $EDITOR for 'amend-commit' isn't trivial
and I cannot insist
On phone, apologies for top posting. To me amend uuid should behave as
much as possible like commit, though I can appreciate that some might
disagree.
On Jul 17, 2015 8:38 PM, Andy Bradford amb-fos...@bradfords.org wrote:
Thus said Sergei Gavrikov on Thu, 16 Jul 2015 17:21:55 +0300:
I also
Hello,
[ unrelated meta-comment follows ]
On 16 July 2015 at 08:19, Stephan Beal sgb...@googlemail.com wrote:
for bonus points (certainly not necessary), allow multiple -tag/-cancel
flags:
...
I'm a gmail-user, and for some reason they seem to have cranked up
their spam-filter settings
On Thu, Jul 16, 2015 at 7:06 AM, Andy Bradford amb-fos...@bradfords.org
wrote:
Hello,
Has anyone (other than me) tested the changes for enabling amending
checkins from the command line in the check-in-edit branch?
I think it's ready, but it certainly could use additional testing given
Hello,
On 16 July 2015 at 07:06, Andy Bradford amb-fos...@bradfords.org wrote:
Has anyone (other than me) tested the changes for enabling amending
checkins from the command line in the check-in-edit branch?
...
FWIW #2, adjusting check-in background colour of tip is pretty much
the only
Thus said Michai Ramakers on Thu, 16 Jul 2015 14:56:49 +0200:
I don't know what the intended behaviour was w.r.t. bogus input on
commandline - e.g. 'fossil amend tip something_bogus' does nothing
(and prints nothing).
Definitely would expect an error here, specifically not
On Thu, Jul 16, 2015 at 4:47 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
Thus said Stephan Beal on Thu, 16 Jul 2015 08:19:00 +0200:
for bonus points (certainly not necessary), allow multiple
f-tag/-cancel lags:
Yes, I considered that but wasn't certain if others would be
On Thu, Jul 16, 2015 at 4:52 PM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, Jul 16, 2015 at 4:47 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
That wouldn't be hard to add, especially if there is already a routine
to check for hexadecimalish. Are there any colors that
On Thu, 16 Jul 2015, Michai Ramakers wrote:
Hello,
On 16 July 2015 at 07:06, Andy Bradford amb-fos...@bradfords.org wrote:
Has anyone (other than me) tested the changes for enabling
amending checkins from the command line in the check-in-edit branch?
Thanks for CLI support. Mostly
Hello,
On 16 July 2015 at 07:06, Andy Bradford amb-fos...@bradfords.org wrote:
Has anyone (other than me) tested the changes for enabling amending
checkins from the command line in the check-in-edit branch?
I think it's ready, but it certainly could use additional testing given
that
Thus said Sergei Gavrikov on Thu, 16 Jul 2015 17:21:55 +0300:
I also expected that 'fossil amend uuid' will spawn $EDITOR with an
original check-in message likes 'fossil commit' does.
That's actually a good idea. The problem with --comment as currently
implemented is that it allows you to
On Thu, Jul 16, 2015 at 11:31 PM, Michai Ramakers m.ramak...@gmail.com
wrote:
I'm a gmail-user, and for some reason they seem to have cranked up
their spam-filter settings recently.
This is one out of a handful of mails (from you, Stephan :-) to the
list, that ended up in my spam-box in
On Jul 16, 2015 2:31 PM, Michai Ramakers m.ramak...@gmail.com wrote:
Hello,
[ unrelated meta-comment follows ]
On 16 July 2015 at 08:19, Stephan Beal sgb...@googlemail.com wrote:
for bonus points (certainly not necessary), allow multiple -tag/-cancel
flags:
...
I'm a gmail-user,
Hello,
Has anyone (other than me) tested the changes for enabling amending
checkins from the command line in the check-in-edit branch?
I think it's ready, but it certainly could use additional testing given
that it also includes changes that affect the web ci_edit page
(primarily
34 matches
Mail list logo
