Re: [fossil-users] List of checkins
Another way, just to add to the list:
echo -e ".mode csv\nselect uuid from event, blob where event.objid=blob.rid
and type='ci' and mtime > julianday('2012-05-27');" | fsl sqlite
-B
On Sat, May 26, 2012 at 5:51 PM, Stephan Beal wrote:
> On Sun, May 27, 2012 at 12:49 AM, Stephan Beal wrote:
>
>> [stephan@host:~/cvs/fossil/fossil]$ f json timeline checkin -b
>> 2012-05-27 -I 1 | awk -F : '/"uuid":/{print $2}' | cut -d'"' -f2
>>
>>
> Slightly more succinct, but should work the same:
>
> f json timeline checkin -b 2012-05-27 -I 2 | grep '"uuid"' | cut -d'"' -f4
>
>
> --
> - stephan beal
> http://wanderinghorse.net/home/stephan/
> http://gplus.to/sgbeal
>
>
> ___
> 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
Re: [fossil-users] List of checkins
On Sun, May 27, 2012 at 12:49 AM, Stephan Beal wrote:
> [stephan@host:~/cvs/fossil/fossil]$ f json timeline checkin -b
> 2012-05-27 -I 1 | awk -F : '/"uuid":/{print $2}' | cut -d'"' -f2
>
>
Slightly more succinct, but should work the same:
f json timeline checkin -b 2012-05-27 -I 2 | grep '"uuid"' | cut -d'"' -f4
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] List of checkins
On Sat, May 26, 2012 at 11:34 PM, wrote:
> Is it possible to get a more "raw" list than 'fossil timeline before
> 2012-05-27 -t ci' out of the command line tool? Would prefer a straight
> list of newline-separated hash values.
>
This is a bit hacky, but...
[stephan@host:~/cvs/fossil/fossil]$ f json timeline checkin -b 2012-05-27
-I 2 | awk -F : '/"uuid":/{print $2}' | cut -d'"' -f2
e130c2e781e4b2cc4364451199f15b04236f61c0
733e9af854ed9c6adf708252d2f746b95841e507
3613fe561355764d4300fcdb4b71f1e5c662
cc008ebab7eda7e7ebc783a2413afcc2105a080d
0141e20ff041bf3f77c2e079f238478a686741ac
b22cc4eb73c34401d74d76627de229e6bb4c5f10
7fb59a67dc6ecf144d29b0d2e9ecff679bd6e034
e2f5be6df11e71fa488aac7bb6078237945bb1f9
59169e4d161379f78cc57d43a586a7b63779fb31
a30da54fee8294366ffe59bb906249a9ed419177
396eceb9e41290e37b4c07817bdcce46e7f60ccf
82332148a2aa3cb6c7272c2708beff50536bf688
02051489a03874d4f16446e8fb58d74711d98cfa
ead316f3f7c88187013619e25fc898be420d4f67
a7a331fa1672aaa37f6ceab673568c288d1e9cf7
55e7e24595982a88ada9e75839e27484fba6a805
20362c85a832af48310cd7edd0a5b3af9c87a834
68a8a7e925e5cf862b4141ed783030b91f9f18e0
42f4d14771b0a7a7b3266febf7c4f011929ee1a0
cb5db7598fdf93b37c3c35661c71908b586e6993
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] List of checkins
Hello. Is it possible to get a more "raw" list than 'fossil timeline before 2012-05-27 -t ci' out of the command line tool? Would prefer a straight list of newline-separated hash values. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Clarification of "not within an open checkout" error message
On Sat, May 26, 2012 at 10:53 PM, Noam Postavsky < npost...@users.sourceforge.net> wrote: > I think the message should be amended to something like "current > directory is not within an open checkout" > Sounds like a good idea... http://www.fossil-scm.org/index.html/info/e130c2e781 :) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Clarification of "not within an open checkout" error message
When I was just starting with fossil I hadn't grasped the distinction between the repository and a checkout so this error message was confusing to me. I read it as "you can't do this operation within an open checkout", rather than the intended "you are not currently within an open checkout". I think the message should be amended to something like "current directory is not within an open checkout". ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Signing
On Sat, May 26, 2012 at 11:30:01AM -0700, Gé Weijers wrote: > On Fri, May 25, 2012 at 10:59 AM, Ron Wilson wrote: > > On top of that, could support signing one or more of the existing > > signatures at the time of signing. > > When I sign a commit, it can mean multiple things: > 1) I wrote this (authentication) > 2) I approve this (authorization) > > In case 1, we have a one-to-one and immutable correspondence between > signature and commit artifact. This signature is the one used to pin > the blame on someone if you find a backdoor in the code :-( > > In case 2, there can be multiple signatures, some after the fact. > These could be used to keep track of code reviews and/or manager > approvals. > > Now If I'm signing your type 2 signature, what does that actually > mean? "I approve of you approving this"? Signing type 1 signatures is > just the 'authorization' type signature. Well, you can always have different signers and multiple signatures. One for authentication, one for authorisation. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Signing
On Fri, May 25, 2012 at 10:59 AM, Ron Wilson wrote: > On top of that, could support signing one or more of the existing > signatures at the time of signing. When I sign a commit, it can mean multiple things: 1) I wrote this (authentication) 2) I approve this (authorization) In case 1, we have a one-to-one and immutable correspondence between signature and commit artifact. This signature is the one used to pin the blame on someone if you find a backdoor in the code :-( In case 2, there can be multiple signatures, some after the fact. These could be used to keep track of code reviews and/or manager approvals. Now If I'm signing your type 2 signature, what does that actually mean? "I approve of you approving this"? Signing type 1 signatures is just the 'authorization' type signature. -- Gé ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
