On Sun, Sep 29, 2013 at 6:14 PM, Chad Perrin wrote:
> My understanding is that the concern raised was about copying (i.e.
> shell command cp, or maybe scp), not syncing.
>
It would only be copied if someone copies their checkout db file, which
would be a highly unusual thing to do. Of course, wh
On Sun, Sep 15, 2013 at 01:52:49PM +0200, Stephan Beal wrote:
> On Sun, Sep 15, 2013 at 12:56 PM, BohwaZ wrote:
>
> > provides that, but it's ok as long as it's not turned on by default and
> > we can clear the history, like before copying a repository file to
> > publish it online.
> >
>
> It's
On Sun, Sep 15, 2013 at 12:56 PM, BohwaZ wrote:
> provides that, but it's ok as long as it's not turned on by default and
> we can clear the history, like before copying a repository file to
> publish it online.
>
It's stored in the checkout db, so it's _never_ synced. The '-c' flag
clears the h
Le Wed, 11 Sep 2013 22:58:56 +0200, Stephan Beal
a écrit :
> If you don't find the idea offensive/abusive, you needn't say
> anything. If you do, please voice your concerns. If there is
> sufficient outcry i'll drop that branch instead of integrating it. If
> we do decide to add it, i will add a
On Thu, Sep 12, 2013 at 12:14:01AM +0200, Stephan Beal wrote:
> On Wed, Sep 11, 2013 at 11:58 PM, B Harder wrote:
>
> > fossil set tracker [on|off] ?
> >
> IIRC "Trac" was Fossil's predecessor for ticket tracking, and "tracker"
> always implies tickets to me (as a by-day/by-night developer).
>
>
[Default] On Wed, 11 Sep 2013 23:32:10 +0200, Stephan Beal
wrote:
>
>> I wouldn't be interested in logging query-class commands, like
>> fossil ls, fossil status, fossil timeline
>>
>
>Do you mean the SQL code itself?
No, I now realize "query" is a confusing word.
I mean the class of commands
fossil set tracker [on|off] ?
On Sep 11, 2013 2:32 PM, "Stephan Beal" wrote:
> On Wed, Sep 11, 2013 at 11:26 PM, Kees Nuyt wrote:
>
>> I wouldn't mind logging the arguments as well, especially for commands
>> that modify the repository or a stash.
>>
>
> i considered it, but the code overhead ju
On Wed, Sep 11, 2013 at 5:56 PM, Kees Nuyt wrote:
> [Default] On Wed, 11 Sep 2013 23:32:10 +0200, Stephan Beal
> wrote:
> >> usage -> commandtrace or commandhistory or cmdtrace or cmdhistory
> >
> > i think 3 of those might mess up the column alignment in 'help' ;).
>
> Yeah, I'm happy with 'cmd
On Wed, Sep 11, 2013 at 5:58 PM, B Harder wrote:
> fossil set tracker [on|off] ?
>
Or 'fossil set cmdhist [on|off]'
Good idea.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fos
On Thu, Sep 12, 2013 at 12:08 AM, Ron Wilson wrote:
> On Wed, Sep 11, 2013 at 5:58 PM, B Harder wrote:
>
>> fossil set tracker [on|off] ?
>>
> Or 'fossil set cmdhist [on|off]'
>
i like cmdhist but my fingers don't like typing it :/. cmdhist. Just feels
awkward to type. Kind of like the word "aw
On Wed, Sep 11, 2013 at 11:58 PM, B Harder wrote:
> fossil set tracker [on|off] ?
>
IIRC "Trac" was Fossil's predecessor for ticket tracking, and "tracker"
always implies tickets to me (as a by-day/by-night developer).
How about...
fossil set nsa-mode on|off
;)
That reminds me (for some reaso
On Wed, Sep 11, 2013 at 11:56 PM, Kees Nuyt wrote:
> I mean the class of commands that doesn't change anything to a
> repository or a checkout is not interesting for logging.
>
That's a very good point - didn't think of that. We could also do this at
the db level - log them all but then create v
On Wed, Sep 11, 2013 at 11:26 PM, Kees Nuyt wrote:
> I wouldn't mind logging the arguments as well, especially for commands
> that modify the repository or a stash.
>
i considered it, but the code overhead just wasn't worth it at that time of
night. One of these days i'll miss having that, add i
Hi, all,
Once 1.27 officially goes out the door, i plan on pulling the new 'usage'
command into the trunk (for 1.28). My question to you is: is there anyone
who finds the idea of fossil recording which commands (not their arguments)
and the times of their usage in the local checkout database offen
[Default] On Wed, 11 Sep 2013 22:58:56 +0200, Stephan Beal
wrote:
>Hi, all,
>
>Once 1.27 officially goes out the door, i plan on pulling the new 'usage'
>command into the trunk (for 1.28). My question to you is: is there anyone
>who finds the idea of fossil recording which commands (not their arg
15 matches
Mail list logo
