I have one more question and a feature request:

1. Ok, so every unique blob.rid points to a unique blob.uuid.
Whats the point in that redundancy? And why are they
declared as 'vid' in the implementation?

2. Shouln't <f stash ls>  (everyone seems to alias it as 'f', I do
as 'fos' :) display the checkouts messages and
checkin uuid to get a clearer overview of what the 'goto'
subcommand will do (which is a bonus, given 'hg shelves'
dont track that info, and sooner or later the stashes will
be inconsistent if the trunk is changing heavily between commits)


2016-04-09 4:39 GMT-03:00 Stephan Beal <sgb...@googlemail.com>:

> On Sat, Apr 9, 2016 at 3:21 AM, fran <brauning...@gmail.com> wrote:
>
>> from the stash structure
>>
>> sqlite> select * from stash;
>> 1|9|invierte logica de isaccepted|2457472.71413265
>> 2|18|test another -l implementacion|2457473.03696663
>> 3|20|directorio DATA|2457473.05750676
>> 4|20|endswith|2457473.49600748
>> 8|52|calculos con let|2457487.53399897
>> sqlite> .schema stash
>> CREATE TABLE stash(
>>   stashid INTEGER PRIMARY KEY,
>>   vid INTEGER,
>>   comment TEXT,
>>   ctime TIMESTAMP
>> );
>>
>> from what I understand those are the baseline
>> ids: the version of checkout when the stash
>> got created. But those dont look like CHECKINS
>> ids.
>>
>
> Your understanding is correct, but they're references to blob.rid, whereas
> blob.uuid is the ID you were likely expecting to see.
>
>
> --
> ----- stephan beal
> http://wanderinghorse.net/home/stephan/
> http://gplus.to/sgbeal
> "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
> those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to