On Thu, Oct 2, 2014 at 3:35 PM, David Mason wrote:
> fossil update -q && fossil update 2>&1 | mail -s 'Fossil update'
> m...@he.re
i've been mulling over this, and there's one fundamental flaw here: if
auto-sync is on (which it is by default), then fossil does not know if
there's work to be
On 10/2/2014 12:57 PM, to...@acm.org wrote:
I tried something very simple (in this example:
https://chiselapp.com/user/rberteig/repository/WPCLI/home), and it
apparently fixed the problem in cloned copy at least.
I shunned the empty initial checking, rebuilt, and re-enabled the
artifact (ju
-Original Message-
From: fossil-users-boun...@lists.fossil-scm.org
[mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Ron W
Sent: Thursday, October 02, 2014 3:35 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] I have two trunks?
On Thu, Oct 2, 2014 at 2:33
On Thu, Oct 2, 2014 at 2:33 PM, dave wrote:
>
> * Its big, so chisel can't import it, but they have a feature where you
> explicitly supply the project id, and then you can sync your big repo into
> it. So I did that.
When I did have a repo on Chisel, I didn't notice this feature. So, what I
> -Original Message-
> From: fossil-users-boun...@lists.fossil-scm.org
> [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf
> Of to...@acm.org
> Sent: Thursday, October 02, 2014 2:58 PM
> To: Fossil SCM user's discussion
> Subject: Re: [fossil-users] I have two trunks?
>
>
>
If it helps:
I tried something very simple (in this example:
https://chiselapp.com/user/rberteig/repository/WPCLI/home), and it
apparently fixed the problem in cloned copy at least.
I shunned the empty initial checking, rebuilt, and re-enabled the artifact
(just in case).
The timeline show
2014-10-02 20:54 GMT+02:00 Andy Bradford:
> The project-id is stored in a table in a database---it can be changed. I
> suspect that this is how Chiselapp actually allows you to sync a new
> repository to their site in some configurations. Because the act of
> creating a new repository nec
> Date: Thu, 2 Oct 2014 13:40:06 -0400
> From: David Mason
> To: "Fossil SCM user's discussion"
> Subject: Re: [fossil-users] Quiet mode for update and sync
> Message-ID:
>
> Content-Type: text/plain; charset=UTF-8
>
> Right, what I wanted to do was get rid of the remote-url. It turns
>
On 2 October 2014 15:04, Andy Goth wrote:
> Type: fossil remote-url off
Ah, much cleaner! Thanks, missed that.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/2/2014 12:40 PM, David Mason wrote:
> Right, what I wanted to do was get rid of the remote-url. It
> turns out that if you say: fossil remote-utl '' it complains that
> it's invalid, but now it's off, so it no longer attempts to sync.
Type: fos
...
> Thus said B Harder on Thu, 02 Oct 2014 11:17:23 -0700:
>
> > Is that even possible? I thought the repo would have to
> be created
> > once (and only once), generating it's repo-id, and then
> cloned for all
> > subsequent copies before things can begin deviating.
>
> The project-id is
Thus said B Harder on Thu, 02 Oct 2014 11:17:23 -0700:
> Is that even possible? I thought the repo would have to be created
> once (and only once), generating it's repo-id, and then cloned for all
> subsequent copies before things can begin deviating.
The project-id is stored in a table in a
Bingo.
On 10/2/2014 11:33 AM, dave wrote:
I'm tending to suspect not (additional trunk at creation) for a reason that
I will soon make clear, but the 'version mismatch' hypothesis is
interesting. Fyi, the creation process went like this:
* I created my repo locally, with current (v1.29,
On 10/2/2014 10:31 AM, Stephan Beal wrote:> The weird thing is, he's got
two "initial empty commits". i'm at a loss
> to explain that.
>
> http://chiselapp.com/user/ziggurat29/repository/z29-3rdParty/timeline
I think I can partly explain the "two initial empty commits" part, or at
least sh
> -Original Message-
> From: fossil-users-boun...@lists.fossil-scm.org
> [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf
> Of Andy Bradford
> Sent: Thursday, October 02, 2014 1:15 PM
> To: Stephan Beal
> Cc: Fossil SCM user's discussion
> Subject: Re: [fossil-users] I have t
Thing is (well, two things): a) I would expect a fork to still have a
common ancestor. I have certainly run across the fork thing due to out of
synced repos (and as I recall, I get a warning beforehand). And b) in this
case I had started from a freshly pulled-down clone, so I never had the
opp
On Oct 2, 2014 11:14 AM, "Andy Bradford" wrote:
>
> Thus said Stephan Beal on Thu, 02 Oct 2014 19:31:12 +0200:
>
> > The weird thing is, he's got two "initial empty commits". i'm at a
> > loss to explain that.
>
> Seems that one of them must have been created with an older fossil and
> the
Thus said Stephan Beal on Thu, 02 Oct 2014 19:31:12 +0200:
> The weird thing is, he's got two "initial empty commits". i'm at a
> loss to explain that.
Seems that one of them must have been created with an older fossil and
the other created with a newer version from Fossil's trunk w
Right, what I wanted to do was get rid of the remote-url. It turns
out that if you say:
fossil remote-utl ''
it complains that it's invalid, but now it's off, so it no longer
attempts to sync.
Thanks ../Dave
___
fossil-users mailing list
fossil-use
On Thu, Oct 2, 2014 at 7:29 PM, B Harder wrote:
> This is a "fork" (unintentional branch). It would happen (for example)
> if two different clones of a repository are updated independently of
> each other, and then sync'd. You can merge the "errant trunk" back to
>
The weird thing is, he's got t
Hi Dave.
This is a "fork" (unintentional branch). It would happen (for example)
if two different clones of a repository are updated independently of
each other, and then sync'd. You can merge the "errant trunk" back to
the "good trunk" without ill effect (minding you might have to do
conflict reso
On Thu, Oct 2, 2014 at 7:02 PM, Goyo wrote:
> 2014-10-02 15:35 GMT+02:00 David Mason :
> > While I'm on fossil sync, is there a way to reset the "sync source"
> > value?
>
> Is "fossil remote-url" what you want?
>
That's the simplest solution, or... i believe what Ron intended was that
you pull
On Thu, Oct 2, 2014 at 8:53 AM, Stephan Beal wrote:
> If there are no explicit objections, i will merge inherit-priv-mark-sub
> into the trunk sometime later today/tonight:
>
> http://fossil-scm.org/index.html/timeline?r=inherit-priv-mark-sub
>
> Management summary: client-side cosmetic/usability
2014-10-02 15:35 GMT+02:00 David Mason :
> While I'm on fossil sync, is there a way to reset the "sync source"
> value?
Is "fossil remote-url" what you want?
Goyo
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.or
On 2 October 2014 11:02, Ron W wrote:
> On Thu, Oct 2, 2014 at 9:35 AM, David Mason wrote:
>> While I'm on fossil sync, is there a way to reset the "sync source"
>> value?
>
> I think, if you provide a URL when sync'ing, Fossil remembers that. That
> said, the script that I use to backup my Foss
Hi list;
Today I opened one of my repos, and expected to see some stuff that is in
'trunk'. However, it was empty as the day it was born. I could see all my
branches via 'branches', and could update to them, but when I would update
to 'trunk' it would always be empty. Odd, I thought, I'm quite
On Thu, Oct 2, 2014 at 11:03 AM, Stephan Beal wrote:
> On Thu, Oct 2, 2014 at 4:53 PM, Ron W wrote:
>
>> As for supporting in-browser wiki rendering, how about adding an option
>> on the New Wiki Page and Edit Wiki Page pages to choose "in-browser
>> rendering"? Then wrap the "raw" wiki mark-up
On Thu, Oct 2, 2014 at 10:03 AM, David Mason wrote:
> I want to expose the wiki and ticket system to the public, but not
> anything to do with the checkins or private wiki pages..
> ...
> Two problems:
>
> 1) the timeline is visible. This could expose information that we
> ...
> 2) the wiki is f
On Thu, Oct 2, 2014 at 4:53 PM, Ron W wrote:
> As for supporting in-browser wiki rendering, how about adding an option on
> the New Wiki Page and Edit Wiki Page pages to choose "in-browser
> rendering"? Then wrap the "raw" wiki mark-up with
> and when "in-browser rendering" is chosen.
>
That's
On Thu, Oct 2, 2014 at 9:35 AM, David Mason wrote:
> While I'm on fossil sync, is there a way to reset the "sync source"
> value? For whatever reason (actually because it was easier to update
> privileges on my laptop than my headless server) I copied a "client"
> fossil to the server and now if
On Thu, Oct 2, 2014 at 8:56 AM, Gour wrote:
> On Thu, 2 Oct 2014 14:43:50 +0200
> Stephan Beal wrote:
> > That said... If you have suggestions for a generic api for arbitrary
> > wiki parsers/filters for libfossil, i am all ears. :)
>
> As I wrote above, no intention for providing general api no
That was unfortunately a bit optimistic of me (i tend towards pessimism in
most estimates ;), for which i apologize. Wiki topics in general are way,
way, way down on my list of eventual todos.
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity and
typos.
On Oct 2, 20
I want to expose the wiki and ticket system to the public, but not
anything to do with the checkins or private wiki pages..
So I set up privileges:
anonymous chmn
nobody jr
Two problems:
1) the timeline is visible. This could expose information that we
don't want. The 'y' privilege cha
I have a server that has a working directory I want to keep current
(because it's web pages that I edit elsewhere).
I want a script to run every 5 minutes and if there is any update,
email me the update log. But I don't want email every 5 minutes that
just says everything is up to date. I can fi
On Thu, 2 Oct 2014 14:43:50 +0200
Stephan Beal wrote:
> i hear you ;), but as i said at the start of this thread, i am
> ambivalent about which format(s) fossil supports, which may be
> interpreted as "i don't care, as long as someone else implements
> it" ;).
Well, I am thinking along these wor
i hear you ;), but as i said at the start of this thread, i am ambivalent
about which format(s) fossil supports, which may be interpreted as "i don't
care, as long as someone else implements it" ;).
That said... If you have suggestions for a generic api for arbitrary wiki
parsers/filters for libfo
On Sun, 28 Sep 2014 16:48:55 -0400
Trevor wrote:
> Markdown is versatile, simple format but the multiplicity of
> "standards" limits its universality. I hope you can contribute
> to the making of such a standard.
I read a bit about the endeavour to make standard version of Markdown,
but here I'd
Chances are when you use FOSSIL_BUILD_SSL you also want to enable SSL.
So, to avoid having to give both FOSSIL_BUILD_SSL and FOSSIL_ENABLE_SSL on the
make command line, I propose something like this change in the win/Makefile.msc:
--- OLD ---
# Uncomment to enable SSL support
# FOSSIL_ENABLE_SSL =
38 matches
Mail list logo
