Hi Andy,
On 08/05/15 23:34, Andy Bradford wrote:
Thus said paul on Fri, 08 May 2015 21:17:36 +0100:
OK, so if I do a merge with baseline, supply two UUID's so that I only
merge the changes for one UUID, are you saying that cherrypick is a
shortcut for that, because you only need to supp
Thus said paul on Fri, 08 May 2015 21:17:36 +0100:
> OK, so if I do a merge with baseline, supply two UUID's so that I only
> merge the changes for one UUID, are you saying that cherrypick is a
> shortcut for that, because you only need to supply one UUID with
> cherrypick?
I see, you'
On 08/05/15 21:03, Andy Bradford wrote:
Thus said paul on Fri, 08 May 2015 20:51:44 +0100:
For example, what's the difference between merge with baseline and
cherrypick? The documentation probably should explain that somewhere.
When you merge, you merge in all changes leading up to tha
On Fri, 08 May 2015 21:14:07 +0200, Abilio Marques
wrote:
Ohhh, I did use dbstat the other day (several times actually) while
working
with some binary files. But yeah, I know there is the -a list, plus the
hidden list. But I'm still happy to know that almost everything I use is
at
hand,
On 08/05/15 21:03, Andy Bradford wrote:
Thus said paul on Fri, 08 May 2015 20:51:44 +0100:
For example, what's the difference between merge with baseline and
cherrypick? The documentation probably should explain that somewhere.
When you merge, you merge in all changes leading up to tha
Thus said paul on Fri, 08 May 2015 20:51:44 +0100:
> For example, what's the difference between merge with baseline and
> cherrypick? The documentation probably should explain that somewhere.
When you merge, you merge in all changes leading up to that baseline
(e.g. if you merge in a
On 08/05/15 20:14, Abilio Marques wrote:
I believe there is room for improvements in the online documentation
too. I want this email chain to be around that idea.
If my memory serves me correctly, fossil help scrub isn't quite right ...
It says that by default only passwords are removed, bu
On 08/05/15 19:29, Warren Young wrote:
I believe sometimes you do understand a thing so much, that you end up
forgetting the explanation.
I think the situation with “merge” is that it’s supposed to just work when run
in the obvious way. You just have to get over your anxiety over the
correct
Ohhh, I did use dbstat the other day (several times actually) while working
with some binary files. But yeah, I know there is the -a list, plus the
hidden list. But I'm still happy to know that almost everything I use is at
hand, and that I don't need a cryptic combination or plainly wrong named
co
On May 7, 2015, at 9:23 PM, Abilio Marques wrote:
>
> One of the things I LOVE about fossil is the simplicity. No weird,
> ultra-hidden cryptic commands that you would use once, perhaps twice in your
> lifetime
Oh, that’s not true.
You may have never said “fossil help -a”, and if you have, I
Very briefly (finger still hurts)...
On Fri, May 8, 2015 at 10:45 AM, Kain Abel wrote:
>
> - introducing a new shortcut 'st' for status (svn compatibility and
> overriding stash)
>
LOL! "st" used to be the short form of "status" until the "st"ash was
added, at which point "st" became ambiguous.
Thank you for opening this thread.
I've found some other items on command line help...
Here are a few things perhaps worthy to discuss:
- exposing abbreviation like ci, co on default help page (the
currently only listed with 'fossil help -a') to avoid unexpected
results (co (checkout) vs. _co_m
On my previous email I said I was looking for a feature in the help. While
being at it, I found out these two details that I want to report.
But first, I want to say something about the help/documentation. One of the
things I LOVE about fossil is the simplicity. No weird, ultra-hidden
cryptic comm
13 matches
Mail list logo
