Thank you again for the answer !
Now I understand the problem, maybe fossil could give an extra bit of info
when it's invoked like "fossil update" maybe something like:
You are now at "branch_name" and it's behind "trunk" by X commits.
?
> Tue Feb 09 2016 6:46:13 pm CET CET from
On Tue, Feb 9, 2016 at 6:16 PM, Domingo Alvarez Duarte <
sqlite-mail at dev.dadbiz.es> wrote:
> Thanks for the answer !
>
> Although it seems a bit weird this behavior of get stuck on one specific
> branch.
>
You might have done 'update tip' at some point when that was the newest.
--
-
Thanks for the answer !
Although it seems a bit weird this behavior of get stuck on one specific
branch.
Cheers !
> OTOH, if that tag is checked out, which your output indicates is the case,
>
>
>>then 'update' will apply no changes because that's the last commit in that
>> branch.
?
> OTOH, if that tag is checked out, which your output indicates is the case,
> then 'update' will apply no changes because that's the last commit in that
> branch. You'll need to 'fossil update trunk' once to get back to the trunk.
>
>
Thanks "fossil update trunk" solved the problem !
Can you try doing this one from the sqlite tree:
>
> fossil pull --verily
>
> in the past that's helped people reporting problems about a repo silently
> failing to pull past a certain version.
>
>
?
fossil pull --verilyPull from http://www.sqlite.org/src
Round-trips: 2?? Artifacts
On Tue, Feb 9, 2016 at 5:38 PM, Stephan Beal wrote:
> fossil pull --verily
>
> in the past that's helped people reporting problems about a repo silently
> failing to pull past a certain version.
>
OTOH, if that tag is checked out, which your output indicates is the case,
then 'update' will
On Tue, Feb 9, 2016 at 5:20 PM, Domingo Alvarez Duarte <
sqlite-mail at dev.dadbiz.es> wrote:
> I frequently follow the updates of fossil and sqlite but I noticed that my
> sqlite clone stop updating the source tree at this commit :
>
Can you try doing this one from the sqlite tree:
fossil pull
Hello !
I frequently follow the updates of fossil and sqlite but I noticed that my
sqlite clone stop updating the source tree at this commit :
fossil status
repository:?? /sqlite3/../sqlite.fossil
local-root:?? /sqlite3/
config-db:?? /.fossil
checkout:
On 2/9/16, Domingo Alvarez Duarte wrote:
> Thanks for the answer !
>
> Although it seems a bit weird this behavior of get stuck on one specific
> branch.
The check-in you were stuck on was originally on trunk. But when an
error was discovered in that check-in, it was diverted to a branch.
You
On 2/9/16, Domingo Alvarez Duarte wrote:
>
> fossil pull --verilyPull from http://www.sqlite.org/src
> Round-trips: 2 Artifacts sent: 0 received: 28
> Pull done, sent: 1090 received: 1579893 ip: 67.18.92.124
>
> After the above I also executed the command bellow and the respository still
>
On 2/9/16, Stephan Beal wrote:
> On Tue, Feb 9, 2016 at 5:38 PM, Stephan Beal wrote:
>
>> fossil pull --verily
>>
>> in the past that's helped people reporting problems about a repo silently
>> failing to pull past a certain version.
>>
>
> OTOH, if that tag is checked out, which your output
11 matches
Mail list logo