On 12/27/15, Richard Hipp wrote:
> My previous patch was not quite right. After a second look, I checked
> in a slightly different fix. I won't be able to test the new fix on
> windows until about this time tomorrow.
>
I can now confirm that the patch checked in yesterday
merges do nothing:
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg20758.html
Original Message
From: Richard Hipp
Sent: Tuesday, 29 December 2015 04:51
To: Fossil SCM user's discussion
Reply To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Show current checkout
Sent: Sunday, December 27, 2015 4:31 PM
Subject: Re: [fossil-users] Show current checkout and branch in Web UI
On 12/26/15, Steve Stefanovich <s...@stef.rs> wrote:
>> >> It only works if you start it without a repository name from within
>> >> an open checkout.
>
My previous patch was not quite right. After a second look, I checked
in a slightly different fix. I won't be able to test the new fix on
windows until about this time tomorrow.
On 12/27/15, Richard Hipp wrote:
> On 12/26/15, Steve Stefanovich wrote:
>>> >> It
-users] Show current checkout and branch in Web UI
My previous patch was not quite right. After a second look, I checked
in a slightly different fix. I won't be able to test the new fix on
windows until about this time tomorrow.
On 12/27/15, Richard Hipp <d...@sqlite.org> wrote:
&g
On 12/26/15, Steve Stefanovich wrote:
>> >> It only works if you start it without a repository name from within
>> >> an open checkout.
>> >
>> > But I do start it from the open checkout directory without arguments,
>> > and it doesn't work ('no such object: current'); tried 1.33
> >> It only works if you start it without a repository name from within
> >> an open checkout.
> >
> > But I do start it from the open checkout directory without arguments,
> > and it doesn't work ('no such object: current'); tried 1.33 and 1.34, on
> Windows.
>
> Works for me on Linux. I'll
> It only works if you start it without a repository name from within an open
> checkout.
But I do start it from the open checkout directory without arguments, and it
doesn't work ('no such object: current'); tried 1.33 and 1.34, on Windows.
___
On 12/23/15, Steve Stefanovich wrote:
>> It only works if you start it without a repository name from within an
>> open checkout.
>
> But I do start it from the open checkout directory without arguments, and it
> doesn't work ('no such object: current'); tried 1.33 and 1.34, on
[Default] On Wed, 23 Dec 2015 06:58:16 +, Steve Stefanovich
wrote:
> In that case, Fossil doesn't know what current means
> (i.e. /info/current returns 'No such object: current'
> and /timeline?c=current just shows 11 latest checkins).
/timeline?n=999
--
Regards,
Kees Nuyt
On 12/23/15, Steve Stefanovich wrote:
>
> Yes, this is helpful - if served by 'fossil ui' it shows the current
> checkout timeline and info that I need.
>
> However, I realised if this is to be visible to all the team, I need to use
> 'fossil server'.
"current" also works with
On Dec 22, 2015, at 11:58 PM, Steve Stefanovich wrote:
>
> if this is to be visible to all the team, I need to use 'fossil server'.
>
> In that case, Fossil doesn't know what current means
In that case, maybe /info/tip gives you what you want.
Beware: “tip” may give surprising
On 12/22/15, Steve Stefanovich wrote:
> Is there a way, if Fossil is running as 'fossil ui' from checkout
> directory, to show which hash and branch the checkout (along with other
> info, like commit timestamp, user and comments) is currently at?
Do the following URLs provide
Is there a way, if Fossil is running as 'fossil ui' from checkout directory,
to show which hash and branch the checkout (along with other info, like commit
timestamp, user and comments) is currently at?
We have multiple checkout builds for different environments, and I would like
to show
Yes, this is helpful - if served by 'fossil ui' it shows the current checkout
timeline and info that I need.
However, I realised if this is to be visible to all the team, I need to use
'fossil server'.
In that case, Fossil doesn't know what current means (i.e. /info/current
returns 'No
15 matches
Mail list logo