On Fri, Apr 15, 2011 at 11:47 AM, Stephan Beal wrote:
> i have a web page in which i use "marker text" next to list entries, where
> the marker's meaning is described in a legend at the top of the page.
> Is it possible, using th1, for me to replace those hard-coded markers with
> the values of a
On Fri, Apr 15, 2011 at 4:08 PM, Stephan Beal wrote:
> On Fri, Apr 15, 2011 at 8:05 PM, Ron Wilson wrote:
>> Are you asking how to update all your wiki pages, or just replace the
>> markers when a wiki page is displayed?
>
> Just to replace them. e.g. at the top of the page
On Mon, Apr 18, 2011 at 3:15 AM, Carlo A. Bertelli (Charta s.r.l.)
wrote:
> some of my users wrote documentation with MSWord and used copy-paste
> to fill in wiki pages (users say that using the web interface to edit
> text would clutter the timeline with incremental changes).
Good to hear you fo
On Tue, Apr 19, 2011 at 12:23 PM, Tony Perovic wrote:
> Looking at Admin|Header, I think that $ is the part I want
> changed. Where is that coming from?
>
>
>
> I need something like:
>
> If $ equals $ then
>
> $ = “Home”
>
> End
>
>
>
> Do I have to learn TH1/TCL?
>
That is what needs to be c
On Tue, Apr 19, 2011 at 3:37 PM, Tony Perovic wrote:
> Clearly, there must be some way of testing the TH code BEFORE editing the
> html scripts. How?
Since TH1 is a subset of TCL, you could test your TH1 code using a TCL
environment. While it would be easy enough to set values for the
Fossil spec
On Wed, Apr 20, 2011 at 4:00 PM, Tomek Kott wrote:
> My development machine is a Win7 x64 machine. The website application I
> develop for I have access to via a webdav connection that is visible as a
> mounted drive in explorer. I use cygwin for access to many linux tasks etc.,
> and I use a term
On Fri, Apr 22, 2011 at 11:59 AM, Richard Hipp wrote:
> You might argue that we should change the definition of leaf to be "A node
> that as no children of any kind (merge or non-merge) with the same branch
> tag." I'm not sure what the consequences of that change would be, but I'm
> betting ther
On Thu, Apr 21, 2011 at 5:14 PM, Felix Wolfheimer
wrote:
> Thanks for your answer. To be more specific: It is no problem to write
> the download page manually. I don't expect fossil to do this for me. But
> when I have the download.html file plus the packages/installers/source
> archives or whatev
On Mon, Apr 25, 2011 at 4:23 PM, Zed A. Shaw wrote:
> Translate the above statement into
> how I would use it to do this:
>
> 1. Joe blow commits and that causes a leaf.
> 2. I pull from joe blow and merge.
> 3.
> 4. There are only named leaves being shown as branches.
If I am understanding
On Mon, Apr 25, 2011 at 4:58 PM, Richard Hipp wrote:
> "Leaf" is purely a UI concept. Fossil does not use leaves internally for
> anything itself (that I can think of off hand.). Fossil keeps track of
> leaves purely so that it can tell the user what the leaves are.
Fossil also issues a "would
On Tue, Apr 26, 2011 at 2:01 PM, Stephan Beal wrote:
> Accidental forks "happen to me" with alarming frequency, and i would never
> notice them without the timeline. They're primarily caused, apparently, by
> my not being careful enough when i disable autosync and work on the same
> code from mult
2011/4/28 Lluís Batlle i Rossell :
> I see that text gets displayed. Shouldn't it better be hidden, as
> normal html would do?
I don't recall if any Wiki has any kind of comment markup, but since
Fossil mostly uses a subset of HTML for its markup, it would make
sense for it to support HTML commen
On Thu, Apr 28, 2011 at 10:16 AM, Stephan Beal wrote:
> 2011/4/28 Lluís Batlle i Rossell
> Richard chose the approach of "don't make them learn another markup
> language, but instead sub-set the single most common format and import a
> small handful of the most common wiki conventions" ("small ha
On Fri, Apr 29, 2011 at 1:29 PM, Stephan Beal wrote:
> On Fri, Apr 29, 2011 at 6:31 PM, Bill Burdick
> wrote:
>>
>> You can access raw wiki pages by getting the id of the wiki page and then
>> using a "raw" URL. You can use a "whistory"
>
> Yes, but that is of limited utility - i don't want to u
On Tue, May 3, 2011 at 10:57 AM, Rene wrote:
> And what really is a lot of work to maintain the html pages in c-src.
> adding javascript complicates that even more. One src file can contain
> C-preprocessor, C language, HTML, TH1 and javascript
I noticed that Richard included a translate utility
On Wed, May 4, 2011 at 3:09 PM, Stephan Beal wrote:
> i thought maybe each child could be a separate fork, and then be changed in
> its own branch of the hierarchy. i have no idea if it's feasible, though.
The parent-child between issues is not the same as between revisions
of an object, which co
On Thu, May 5, 2011 at 4:21 AM, Felix Wolfheimer
wrote:
> Is there a simpler way to find the artifact
> number of a wiki page using the fossil web interface?
There could be multiple artifact IDs for a wiki page as Fossil tracks
changes to wiki pages like it would commits toa file, so you would
ha
On Sat, May 21, 2011 at 4:29 PM, Gour-Gadadhara Dasa wrote:
> On Sat, 21 May 2011 14:32:34 -0400
> Richard Hipp wrote:
>> Does anybody have any other suggestions on how to prevent the lose
>> of uncommitted work?
>
> Maybe not suggestion to prevent losing of uncommitted work, but I'm
> thinking a
On Mon, May 23, 2011 at 3:25 PM, Stephan Beal wrote:
> The most significant caveat, i think, is that because it's 100%
> client-rendered, and fetching the pages requires processing JSON fetched via
> AJAX, it does not degrade gracefully (at all) for "lesserly capable"
> clients.
Very interesting
2011/5/24 Natacha Porté :
> As a fossil user, I would love to have the option to use Markdown in the
> wiki (with the option of dumbing down to forbid inline HTML which might
> be unsafe -- exactly the same option as it exists today).
To me, the benefit of a more conventional wiki syntax wiould be
On Fri, May 27, 2011 at 3:07 AM, Rene wrote:
> I earlier said to down grade to an older version of fossil.
> Richard warns on
> http://www.fossil-scm.org/fossil/event/a1f9f17b6 (The Irreversible
> Schema Change)
> That it is not an option.
Maybe run the newer Fossil in server mode and clone the r
I would use it. I'd do a search of the source code, but not convenient
for me right now.
On Sat, May 28, 2011 at 2:12 PM, Stephen De Gabrielle
wrote:
> Hi, does anyone use "contact info" at all?
>
> I'm keen to use it in the ticket templates, but I don't know how to
> reference it.(I can't find i
On Mon, May 30, 2011 at 3:43 AM, Remigiusz Modrzejewski
wrote:
> But I still believe, that the true problem is storing in the repository
> things that are not part of the project...
He did not say they were not part of the project.
But anyway, maybe this "optional" part of the project could be
On Fri, Jun 3, 2011 at 10:04 AM, Tony Perovic wrote:
> Ingo is right, a Windows service is a special type of executable.
> Fossil..exe is an “ordinary” Windows executable. But you cannot have Fossil
> just idling, waiting for commands. Fossil just does what the command line
> arguments tell it to
On Fri, Jun 10, 2011 at 12:50 PM, David Bovill wrote:
> Thanks for the replies - so it seems I won't have to worry about managing
> open connections (and I'll have to track down that bug a bit more - probably
> in my scripts :)
I have not had problems, not even with nested working copies (That is
On Tue, Jun 14, 2011 at 3:37 AM, dieter roelants wrote:
> On Mon, 13 Jun 2011 15:24:28 -0700
> "Higham, Paul" wrote:
>
>> but I suspect that TH1 has neither dictionaries nor the {*} operator.
>> How about
>>
>> set oneDlist ""
>> foreach pair $twoDlist {lappend oneDlist [lindex $pair
On Wed, Jun 22, 2011 at 3:52 AM, Ron Aaron wrote:
> I'm trying to get fossil adopted in my company; and one of the
> "problems" is the spartan nature of the diffs (in the GUI).
>
> I'm going crazy trying to overcome the command-line-phobia of my
> coworkers; please, anything you can do to help me
On Mon, Jul 18, 2011 at 4:52 PM, Stephan Beal wrote:
> On Mon, Jul 18, 2011 at 10:51 PM, Richard Hipp wrote:
>>
>> something more distinctive? Perhaps "fossil wservice" or "fossil
>> win-serve". Other ideas?
>
> i'd prefer win-service, but i don't use windows so i don't get a vote.
win-service
On Mon, Jul 18, 2011 at 6:52 PM, Richard Hipp wrote:
> On Mon, Jul 18, 2011 at 6:41 PM, Joan Picanyol i Puig wrote:
>> I've stumbled upon a situation in which fossil's "latest wins" merge
>> strategy and a system's "far-in-the-future" clock have messed up my
>
> If the second paragraph does not de
On Tue, Jul 19, 2011 at 4:50 AM, Joan Picanyol i Puig
wrote:
> Many thanks for your answers, it turns out I got extremely confused by
> not paying enough attention to a fossil warning.
Did Fossil give a warning about the times between the 2 PCs not being in sync?
_
On Wed, Jul 20, 2011 at 4:14 PM, Remigiusz Modrzejewski
wrote:
>
> On Jul 20, 2011, at 21:18 , Eric wrote:
>>
>> 1) there's no pleasing everybody (we all have our different favourites)
>
> But most people agree that any of markdown/restructuredtext/dokuwiki/whatever
> simple syntax is nicer than
On Fri, Jul 22, 2011 at 9:50 AM, Stephan Beal wrote:
> On Fri, Jul 22, 2011 at 2:54 PM, Remigiusz Modrzejewski
> wrote:
>>
>> By the way: this is one of the more cumbersome things about the UI. I'd
>> really like to see this done automatically. But then again, I don't feel
>> like wasting my time
On Mon, Jul 25, 2011 at 2:26 PM, Russ Paielli wrote:
> I am wondering how good Fossil is for code review on a large project. (I am
> a Fossil user, but I am currently only using it in the most basic way, for
> my own project with no collaboration.)
If your developers are making commits to their o
On Tue, Jul 26, 2011 at 5:34 PM, Russ Paielli wrote:
> http://www.fogcreek.com/kiln/features/code-reviews.html
>
> It's just something I stumbled across surfing the web. I have no idea how
> good it is or whether it makes any sense at all to add something like this
> to Fossil.
Possibly something
2011/8/3 Yujianbin
> D:\o is server, D:\m is client.
>
> ** **
>
> The content of tst_server.bat is:
>
> md D:\o
>
> cd /d D:\o
>
> if exist ops del /q ops
>
> if exist _FOSSIL_ del /q _FOSSIL_
>
> fossil version
>
> @echo Please record the password and set it into ts
On Tue, Aug 9, 2011 at 10:58 AM, Richard Hipp wrote:
> The way I've *always* done things is:
>
> (1) ... edit files
> (2) fossil commit -branch new-branch
>
> But I see many people want to do a 4-step process:
>
> (1) fossil branch new new-branch
> (2) fossil update new-branch
On Tue, Aug 9, 2011 at 2:47 PM, Richard Hipp wrote:
> On Tue, Aug 9, 2011 at 2:33 PM, Gé Weijers wrote:
>> If you create the branch first you cannot forget later and commit to the
>> wrong branch.>
> I beg to differ! Just this past Friday, I did three separate commits to
> SQLite that went into
On Mon, Aug 22, 2011 at 7:18 AM, Martin Gagnon wrote:
> Look interesting, but may be overkill for what I want to do. It's only
> because we are like 3 admin that have root access and sometime.. it's
> good to have history of changes on some configuration files to
> understand why and when a change
You can add this by editing the Header.
On Mon, Aug 22, 2011 at 5:09 PM, Jos Groot Lipman wrote:
> When you are not logged in the timeline, branches, and tags pages show a
> useful "Use anonymous login to enable hyperlinks." link.
>
> Can this also be added to the Tickets page(s)? It would be us
On Tue, Aug 30, 2011 at 11:43 AM, Richard Hipp wrote:>
> Is there any reason to "dryrun" a pull? Maybe we should make the automatic
> pull happen even if the -n option is specified?
>
> Note that predicting what an "update" would do after a pull without actually
> doing the pull first would be ra
On Fri, Sep 2, 2011 at 1:02 PM, Clark Christensen wrote:
> FWIW, Fossil does allow you to add fields to the ticket table, markup to the
> ticket create/edit/view pages, and customize the ticket reports. So it
> seems like you could add your own field for storing your custom timestamp,
> and updat
On Tue, Sep 6, 2011 at 4:21 PM, Martin S. Weber wrote:
> (and many, many, many, many more lines like that). This seems to be because
> of the calls to asm() ... I don't know how to fix that. FYI, after
> preprocessing, the first instruction of line 104 looks like:
>
> qq[4]+=((qq[1]&(qq[2]^qq[3])
I guess I'm too used to dealing with dumb compilers.
1. Does it work with the C89 restrictions turned on?
2. Does C89 support inline functions?
3. If not, will it handle the folowing correctly?
#define rotateLeft(x,n) { unsigned int t; t = x >> (SIZEOFINT -
n); x = (x << n) | t; } /* bitw
For me, making it easier to create an IDE plug-in for Fossil would be
the greatest benefit.
Also, I agree that HTTP status codes should be for transport rather
than application errors.
On Thu, Sep 8, 2011 at 4:01 PM, Stephan Beal wrote:
___
fossil-user
On Fri, Sep 9, 2011 at 2:46 PM, Martin S. Weber wrote:
> ... and c) a separation of concerns (you, fossil library, take care of
> the fossil stuff, I take care of invoking hooks, presenting ...
I think that invoking hooks would be an intermediary between the
client and a "pure Fossil" server. Kee
On Sat, Sep 10, 2011 at 1:53 PM, Richard Hipp wrote:
> The hook mechanism should include a delay. This is because client-to-server
> push operations can occur in multiple stateless steps, and we really want to
> wait and run the hooks after all steps of the push operation are complete.
> So, for
On Thu, Sep 8, 2011 at 4:08 PM, Ingo Koch wrote:
> Take a look at
> http://arnebachmann.pytalhost.de/pdf/integrated-version-control-with-fossil-scm.pdf
Good presentation.
I noted it said that configuration is not shared. Actually, it is
possible to share configuration between Fossil instances.
_
On Sat, Sep 10, 2011 at 4:49 PM, Gé Weijers wrote:
> I don't like timers like that, a single server may have clients on fast...
>
> It's been a while since I looked at the protocol specs, but the client
> usually maintains (implicit) state in this type of protocol, and could very
> well indicate t
On Sun, Sep 11, 2011 at 12:23 AM, Stephan Beal wrote:
> On Sun, Sep 11, 2011 at 4:19 AM, Clark Christensen
> wrote:
>> In my experience writing both JSON web services (in Perl), and the
>> consumers of those services, sometimes you can get output that contains not
>> only a JSON string, but stray
On Mon, Sep 12, 2011 at 8:36 PM, Joshua Paine
wrote:
>>
>> I would strongly oppose breaking compatibility with every JSON processor
>> in the world (and, frankly, looking like idiots to people curious about
>> fossil's web services) to possibly protect against some badly behaved
I am surprised th
On Mon, Sep 12, 2011 at 11:50 AM, Richard Hipp wrote:
> Anchor tags in HTML are just one mechanism for providing hyperlinks. In
> JSON, you could just as easily invent an alternative mechanism. Perhaps an
> object:
>
> {
> "LinkType": "Next",
> "URI": "http://www.fossil-scm.o
On Tue, Sep 13, 2011 at 4:30 AM, Alaric Snell-Pym
wrote:
> by context, but it might be worth including JSON and human-HTML versions
> of each URL, like so:
>
> {
> ...stufff about a commit...
> "parents" : {
> "" : { "json" : "http://..json";, "html"
> : "http://...html"; },
> ""
On Mon, Sep 12, 2011 at 6:44 PM, Stephan Beal wrote:
> On Tue, Sep 13, 2011 at 12:35 AM, Ron Wilson wrote:
>>
>> I would add "LinkDescription":"description" to that, or possibly
>> "LinkDescription":"URL", but usually the description
On Wed, Sep 14, 2011 at 12:27 PM, Stephan Beal wrote:
> b) For non-login JSON requests, first check the request info (GET/POST) for
> an authorization token. If found, i need to be able to tell fossil, "here's
> your cookie - use this one." i.e. i need to be able to make fossil think it
> got a co
On Wed, Sep 14, 2011 at 6:40 PM, Stephan Beal wrote:
> Hi, all!
> Just implemented...
> Request:
> GET: /json/login?n=name&p=pass
> Param names "n" and "p" are for compatibility with the current usage, and
> may optionally be written out as "name" and "password".
> or POST: /json/login
> POST requ
On Thu, Sep 15, 2011 at 8:32 AM, fossil-m...@h-rd.org
wrote:
> I think including links etc. gets baroque pretty fast, and different use
> cases require different links. It may be better in the long run to simply
> add a kind of template mechanism to the server. This is explained on p. 297
> in "
On Thu, Sep 15, 2011 at 6:20 PM, Stephan Beal wrote:
> For /json/wiki/list requests, what page info needs to be returned?
> i was thinking:
> name, sizeInBytes (as opposed to size in UTF8 chars), name of last
> committer, artifact ID
> i'm not sure i can get the committers name easily, but the res
On Fri, Sep 16, 2011 at 3:58 AM, Stephan Beal wrote:
> On Fri, Sep 16, 2011 at 5:48 AM, Ron Wilson wrote:
>>
>> Actually, Fossil fetches wiki pages by name. Artifact Id would be used
>> to fetch a specific version of a page
>
> Sorry, i meant when we get a list of page
On Mon, Sep 19, 2011 at 1:19 PM, Stephan Beal wrote:
> Hi, all!
> Which data format would you prefer to see in the up-coming /json/dir output:
If outputing the content of a single directory, then my first
preference is #1. My second preference is #2a.
If multiple directories are being listed, th
On Tue, Sep 20, 2011 at 6:06 PM, Martin S. Weber wrote:>
> As I've written earlier, I'd really like to see a list of all the commands
> and subcommands of tcl on one side, and all of the commands and subcommands
> of jim on the other side, and an indicator whether a) jim does not support
>
> If I
On Mon, Sep 26, 2011 at 11:12 AM, Dmitry Chestnykh
wrote:
>> Should I make a point of always building future Fossil releases using MinGW
>> instead of MSVC?
>
> If there are no issues with MinGW binaries, then I think, yes.
>
> Any Windows users want to chime in?
My team does development for non
On Wed, Sep 28, 2011 at 8:53 AM, Dmitry Chestnykh
wrote:
> Richard wrote:
>> I already checked in a change that sets the timestamp based on the check-in
>> time. But I like your patch better (since it is simpler).
>
> Anyway, your change is better in case the are ungzip implementations that do
On Fri, Sep 30, 2011 at 6:43 AM, Dmitry Chestnykh
wrote:
> I'm mostly concerted about cookies, as it's impossible to time non-plain-text
> passwords -- the
> attacker simply cannot supply passwords which, when hashed, have a few bytes
> of hash
> modified (that is, when you supply "password", th
Congrats. Great work.
On Fri, Sep 30, 2011 at 12:56 PM, Stephan Beal wrote:
> Hi, all!
> In the json branch, under ajax/i-test, i've started adding integration-style
> tests which run against a fossil server or CGI. It uses the Rhino JS engine
> to implement the connection logic, but uses the sam
On Fri, Sep 30, 2011 at 2:27 PM, Dmitry Chestnykh
wrote:
> The attacker cannot supply hash, he supplies password. To do timing attack,
> the
> attacker have to find a such string, for which the hash has a few bytes
> changed.
You and I seem to be talking about different use cases, There are
sce
On Tue, Oct 4, 2011 at 3:59 PM, Richard Hipp wrote:
> Fortunately, there was still one other copy in the undo stack
I would add a fourth lesson: Always backup your work.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fo
2011/10/12 Lluís Batlle i Rossell :
> I never felt the need of using propagating tags (other than branch or
> bgcolor); I
> simply use branches. Can you explain how do you use propagating tags? (not
> only
> Stephan - anynoe using those). I can't say I understand what Stephan meant by
> simply lo
2011/10/20 Lluís Batlle i Rossell :
> On Thu, Oct 20, 2011 at 11:31:01AM -0700, Mike Meyer wrote:
>> Hmm - maybe the "readonly-glob" setting is enough? If it's not set, you get
>> the current behavior. Otherwise, you check it when you pull files out of the
>> repository (to set them read-only) or c
On Wed, Nov 2, 2011 at 6:16 AM, Gilles wrote:
> On Wed, 02 Nov 2011 04:23:20 +0100, Gilles
> wrote:
>>C:\Projects>fossil gdiff --from d4980ff4a7 --to 7c50b63ab5
>>"Project1/Form1.vb"
>>=> WinMerge opens, but files aren't displayed.
>
> Is there a way to check what parameters Fossil uses to call t
On Fri, Nov 11, 2011 at 11:08 AM, Richard Boehme wrote:
> My local fossil copy is at C:\Users\Richard Boehme\Dropbox\apps\bin
Are you using Dropbox to backup your repository? Is it possible
Dropbox is doing something that interferes with Fossil?
___
fos
On Sun, Nov 13, 2011 at 4:33 PM, Julian Fagir wrote:
>
> So, my question: Do you think fossil is appropriate?
It really depends on your and your customers' needs. It works well for
decent number of projects. Certainly has has served the needs of the
projects my coworkers and I work on. I was able
On Wed, Nov 16, 2011 at 4:15 PM, Jacek Cała wrote:
> and wonder why
> fossil is by default so humble to not include a link to its web site
> in the footer.
Maybe to encourage users to contact their project leader first?
In my team, I've been handling the questions.
__
On Thu, Nov 17, 2011 at 12:28 PM, Stephan Beal wrote:
> On Thu, Nov 17, 2011 at 6:02 PM, ST wrote:
>>
>> as far as I understand one can enable/disable ticket viewing completely,
>> but I don't see a way for a user to be able to see/comment/append _only_
>> to tickets submitted by him...
>
> Fossi
On Thu, Nov 17, 2011 at 6:56 PM, Remigiusz Modrzejewski
wrote:
>
> On Nov 17, 2011, at 6:28 PM, Stephan Beal wrote:
>> Fossil doesn't offer that level of granularity.
>
> But it should have, as this seems to be a really reasonable (and perfectly
> doable) thing to have. Thus I open a ticket (sorr
On Fri, Nov 18, 2011 at 5:28 AM, Stephan Beal wrote:
> On Thu, Nov 17, 2011 at 10:55 PM, Ron Wilson wrote:
>>
>> if {$login eq $submitter} {
>> things that only the submitter is allowed to do
>> }
>>
>> You could do similar with an assignedto field,
On Fri, Nov 18, 2011 at 5:36 AM, Remigiusz Modrzejewski
wrote:
>
> You know that by similar funny "implications" we can "prove" that most of
> Fossil is actually
> redundant... Actually, why do we even have a permission system, if Fossil is
> an internal
> development tool?
Last I looked, the
e able to contribute (beyond the small bits of TH1
code I've posted to this list).
On Fri, Nov 18, 2011 at 10:23 AM, Stephan Beal wrote:
> On Fri, Nov 18, 2011 at 4:02 PM, Ron Wilson wrote:
>>
>> In most work environments, I would not expect users outside of the
>> softwar
On Sat, Nov 26, 2011 at 11:03 AM, Jeremy Cowgar wrote:
> I wonder if you cannot use an adaptive technique of checking the last
>
> If the rapid request count hits a predefined threshold, say 5 or 10, flip
> the user to a bot status disabling links... Just an idea.
Except that by then the robot a
On Mon, Nov 28, 2011 at 9:56 AM, Gé Weijers wrote:
> One approach I have seen is to add a link that when traversed classifies the
> IP address as belonging to a robot. It could be put on the timeline page,
> preceded by a warning not to follow the link.
I like this idea, but my earlier comment ab
On Fri, Nov 25, 2011 at 5:02 PM, Barry Kauler wrote:
> My question is, if I have 'allow-symlinks' in the online repository,
> shouldn't the clone operation inherit that? To not inherit it, seems
> to defeat the purpose.
Try:
fossil configuration pull woof2.fossil
after you do the clone.
___
On Thu, Dec 15, 2011 at 3:56 PM, Matt Welland wrote:
> Based on what I've tried so far fossil ui will *always* choose the first
> user listed in the user table. None of $USER, --user, -U, default-user in
> global-config or in config will override fossil ui using the first user
> listed.
>>
> I gue
On Fri, Jan 20, 2012 at 9:00 AM, Bill Burdick wrote:
> The Markdown discussion got me thinking and, as is my wont, I decided to try
> adding Markdown to Fossil without changing the executable. I think I got
>
> To make a wiki page use Pagedown (from the fossil wiki or from a "doc"
> page), just p
On Wed, Jan 18, 2012 at 1:57 PM, Williams, Brian
wrote:
> Typically, one creates the correctly named page and abandons the original…
>
> On Jan 18, 2012 5:15 AM, "Matt Young" wrote:
>
> I Added a wiki page, I accept the changes then discover you want to edit the
> wiki page name. How does one do
On Sun, Feb 5, 2012 at 2:47 PM, Lluís Batlle i Rossell wrote:
> On Sun, Feb 05, 2012 at 02:34:30PM -0500, Leo Razoumov wrote:
>>
>> IMHO, a very important feature is still missing from fossil -- an
>> ability to push or pull a single branch.
>> A great variety of workflows could immediately become
On Sun, Feb 5, 2012 at 2:34 PM, Leo Razoumov wrote:
>
> IMHO, a very important feature is still missing from fossil -- an
> ability to push or pull a single branch.
> A great variety of workflows could immediately become possible.
Perhaps more useful would be the ability to pull a contributor's t
On Mon, Feb 6, 2012 at 1:53 PM, Lluís Batlle i Rossell wrote:
> On Mon, Feb 06, 2012 at 01:07:30PM -0500, Ron Wilson wrote:
>>
>> Mark your branch private.
>>
>> Anything you want to push can then be merged into a non-private branch.
>
> Ah, well, that's fin
On Sun, Feb 26, 2012 at 11:21 AM, Gour wrote:
> On Sun, 26 Feb 2012 09:25:17 -0400
> Chris Peachment wrote:
>
>> It looks to me like you could add a new field to the 'ticket' table,
>
>> The missing part is some way to pass the patient id to the report so
>> that it selects only tickets for the g
On Tue, Feb 28, 2012 at 5:34 PM, Nolan Darilek wrote:
> followed the same code path, we'd be golden? Then all other interfaces be
> they command line or JSON could require that you opt into whatever other tag
> types you'd like.
This makes a lot of sense. Not automatically give everything, but do
Looks good.
On Sun, Mar 11, 2012 at 2:04 PM, Stephan Beal wrote:
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On Mon, Mar 5, 2012 at 10:09 AM, Emil Totev wrote:
> My expectations were that `stash gdiff ` would work like the regular
> `gdiff` and allow to change the working copy. Other should also step
> in to say if this is really something important that needs to be
> optimised.
This makes sense to me,
On Wed, Mar 28, 2012 at 9:42 AM, mlfconv wrote:
> it's about importing an ancient project where all source code files are
> updates and branches to the same file, except no version control software
> was used at that time, and I'd like to import it so no history rewriting
> would happen. Instead o
On Wed, Mar 28, 2012 at 12:54 PM, mlfconv wrote:
> basically i don't want Fossil to perform a merge of A2 and B2 (A is the
> master branch) but insert another file which only acts as a merge and is
> tagged or labeled as merge but no actual merge is performed by Fossil, A3 is
> only inserted inste
Try running fossil in UI or server mode, then try the URL
"http://127.0.0.1:8080/wcontent";
On 5/7/12, Ron Aaron wrote:
> Is there some easy way to find "orphaned" wiki pages? That means: pages
> which cannot be reached from another page.
>
> I'm working with a person who is prolifically inserti
On 5/10/12, Cunningham, Robert wrote:
> An aside: My main motivation is to avoid having to select Trac in the near
> term merely because of Fossil usability issues. If I do have to temporarily
> select Trac while Fossil usability matures, it would be a massive benefit if
> there would one day al
translate TRAC's wiki markup to
Fossil's or a markup supported by a client side wiki renderer.
On 5/10/12, Ron Wilson wrote:
> On 5/10/12, Cunningham, Robert wrote:
>> An aside: My main motivation is to avoid having to select Trac in the
>> near
>> term merely bec
On 5/11/12, Cunningham, Robert wrote:
> Hmmm... Would having a Fossil plugin for Trac simplify conversion from Trac
> to Fossil?
>
> I'm woefully ignorant of what is needed to create a Trac plugin, but the
> command-line power of Fossil ought to simplify the task, right?
Assuming this is a new d
I have never had a problem with Fossil working through an HTTP proxy
server. Unfortunately, I don't know what proxy server is currently
used at my workplace, so I can't cite it as an example. I can say that
Fossil worked through a proxy the first time with no support from IT.
On 5/11/12, Urmil Pa
On 5/7/12, Mike Meyer wrote:
> On Mon, 7 May 2012 14:16:59 +0200
> Jiri Navratil wrote:
>
>> I made a typo in Wiki page. Can I rename Wiki page or delete a Wiki page?
>
> In one sense, no. Artifacts are forever (though you can shun
> them). However, if you delete all the text from a page, it'll v
On 5/15/12, James Masters wrote:
> Sorry, I missed the crucial step of adding and comitting dir_b as a
> symlink. Please append this to my example above:
>
> % fsl add dir_b
> ADDED dir_b
> % fsl commit dir_b -m 'adding symlink'
> ADDED dir_b
> ...
> % fsl ann dir_b/foo
> fossil: no such fi
On 5/22/12, Lluís Batlle i Rossell wrote:
>
> Yes, and there also appears a bit of discussion on "what to sign".
>
> We may want to sign, among some:
> - The tree of files of a specific checkin (signing the checkin hash is
> enough)
> - The tree + comment + date + tags... that would mean a set of
101 - 200 of 389 matches
Mail list logo
