Re: [fossil-users] fossil v1.34 unexpected CLEAN command changes from v1.33

On 11/3/15, Tony Papadimitriou wrote: > Thanks. > > BTW, the help for clean shows this (which is a bit misleading): > > --no-prompt This option disables prompting the user for input and > assumes an answer of 'No' for every question. > > But, if prompting is disabled by

Re: [fossil-users] xkcd on git

On 2 November 2015 at 18:20, Scott Robison wrote: > > Given that the git cli interface was the only interface for humans from the > start, I dare say it was meant for humans. > Any git reference I have seen has that notion of 'porcelain' and 'plumbing' with plumbing

Re: [fossil-users] fossil v1.34 unexpected CLEAN command changes from v1.33

Thanks. BTW, the help for clean shows this (which is a bit misleading): --no-prompt This option disables prompting the user for input and assumes an answer of 'No' for every question. But, if prompting is disabled by default, how does that disable it further? -Original Message-

Re: [fossil-users] impersonating users

On 11/3/15, Eduard wrote: > Hi, > > It seems that anyone with checkin privileges can push anything to a > fossil server, including artifacts that claim to come from other users. > I understand why this is (I'm not complaining); I just want to know > whether there's

Re: [fossil-users] symlinks (was Re: xkcd on git)

On Tue, Nov 3, 2015 at 12:33 AM, Stephan Beal wrote: > On Mon, Nov 2, 2015 at 6:32 PM, Eric Rubin-Smith wrote: >> A user who only ever uses fossil on unix should get unix symlink semantics >> on unix, without quirks or surprises. Surely you and DRH

Re: [fossil-users] symlinks (was Re: xkcd on git)

On Tue, Nov 3, 2015 at 1:33 AM, Stephan Beal wrote: > > On Mon, Nov 2, 2015 at 6:32 PM, Eric Rubin-Smith > wrote: > >> the user when trying to move a tarball from one OS to another. In other >> words, I believe that you perceive a dichotomy that is

Re: [fossil-users] symlinks (was Re: xkcd on git)

> > > Just to clarify, what are the behavioral changes needed on the Unix side to > make > things work seamlessly? > (1) Default allow-symlinks to true (2) Fix bug in which the allow-symlinks setting is not honored while opening a repository (requires manual clean-up of symlinks after opening a

[fossil-users] meeting tomorrow at 10:00?

Hi, Would meeting Wednesday (tomorrow) at 10:00 be okay with you? Please reply to let me know (unless you've filled in the scheduling poll or already told me in person). Cheers, Eduard signature.asc Description: OpenPGP digital signature

[fossil-users] handling backports

Hi, I have some questions as to the 'correct' way of handling backports. Scenario 1: Suppose a really terrible bug (e.g. an exploitable vulnerability) is discovered. Although the latest release is version 2.47, it affects every version from 2.12 onwards. Trunk gets quickly patched and a new

Re: [fossil-users] symlinks (was Re: xkcd on git)

On Tue, Nov 3, 2015 at 9:40 AM, Eric Rubin-Smith wrote: > > - Symlinks. Now we're getting into file system specifics. Some users >> may want to track them because they find them useful. What about users >> that find FIFOs or block devices or character device useful? Should >>

Re: [fossil-users] symlinks (was Re: xkcd on git)

On 3 November 2015 at 10:48, Eric Rubin-Smith wrote: > > On Tue, Nov 3, 2015 at 1:33 AM, Stephan Beal > wrote: >> >> i can't speak for Richard, but if i had my way, fossil wouldn't support >> symlinks at all. >> > This would force me to stop using

Re: [fossil-users] impersonating users

On 11/03/2015 06:38 AM, Richard Hipp wrote: > On 11/3/15, Eduard wrote: > > The artifact receipt log (/rcvfromlist) shows *all* artifacts that > have been received. But it does not filter by artifact type or user - > it shows everything. > > The list-of-artifacts

Re: [fossil-users] Can't build Fossil 1.34 with Tcl 8.5

Trying "make distclean" did not help, the error persisted. #define Tcl_Canceled(a,b) TCL_OK did its job well. :) Thanks, Joe! Pozdrawiam / With best regards, Orzech W dniu 03.11.2015 o 04:34, Joe Mistachkin pisze: > Did you try "make distclean" first? > I wrote both the Tcl and Fossil code in

Re: [fossil-users] fossil v1.34 unexpected CLEAN command changes from v1.33

why is 10mb a magic number? Why have a magic number at all? Scott Doctor sc...@scottdoctor.com -- On 11/3/2015 5:20 AM, Richard Hipp wrote: On 11/3/15, Tony Papadimitriou wrote: Thanks. BTW, the help for clean shows this (which is a bit

Re: [fossil-users] symlinks (was Re: xkcd on git)

David Mason wrote: > > Exactly. Please fix symlinks so that if you live only on Unix you get seamless > support. If you work back and forth between Windows and Unix then you probably > just don't use symlinks, so it won't be a problem for you! > To All: Just to clarify, what are the

[fossil-users] Suggestions for fossil tickets search page

Hello, I would like to submit two suggestions regarding the search page for tickets. It may be just a matter of configuring Fossil, I don't know. To illustrate, I use the Tk fossil repository from the 'Ticket Search' page: http://core.tcl.tk/tk/ticket 1. Is it possible to display on this

Re: [fossil-users] handling backports

On Nov 3, 2015, at 11:48 AM, Eduard wrote: > > Scenario 1: Suppose a really terrible bug (e.g. an exploitable > vulnerability) is discovered. Although the latest release is version > 2.47, it affects every version from 2.12 onwards. Trunk gets quickly > patched and

Re: [fossil-users] xkcd on git

On 3 November 2015 at 22:31, Warren Young wrote: > On Nov 3, 2015, at 5:59 AM, Michal Suchanek wrote: >> >>> Note that detached head state is impossible in Fossil and in most >>> other VCSs. (Unsure about Hg.) >> >> Detached head state is the state which

Re: [fossil-users] handling backports

On 11/3/15, Warren Young wrote: > On Nov 3, 2015, at 11:48 AM, Eduard wrote: >> >> Scenario 1: Suppose a really terrible bug (e.g. an exploitable >> vulnerability) is discovered. Although the latest release is version >> 2.47, it affects every

Re: [fossil-users] symlinks (was Re: xkcd on git)

Eric Rubin-Smith wrote: > > (1) Default allow-symlinks to true > (2) Fix bug in which the allow-symlinks setting is not honored while > opening a repository > Please try the latest Fossil trunk and let us know if that fixes all the issues you were seeing. -- Joe Mistachkin

Re: [fossil-users] symlinks (was Re: xkcd on git)

On Nov 3, 2015, at 2:51 PM, Joe Mistachkin wrote: > > Please try the latest Fossil trunk and let us know if that fixes all the > issues you were seeing. Version c985d905c6 still fails the test case I posted here yesterday:

Re: [fossil-users] xkcd on git

On Nov 3, 2015, at 5:59 AM, Michal Suchanek wrote: > > On 2 November 2015 at 20:40, Richard Hipp wrote: >> On 11/2/15, Michal Suchanek wrote: >>> >>> when you >>> want to separate the changes you want to commit and changes you want >>>

Re: [fossil-users] xkcd on git

On Nov 3, 2015, at 3:16 PM, Michal Suchanek wrote: > > This is nice example of out of context quoting. No, it’s an example of trimming quotes because it is only necessary to remind people what was being said, since it’s 2015 and we all have mailers with history scrollback

Re: [fossil-users] symlinks (was Re: xkcd on git)

On Tue, Nov 3, 2015 at 4:51 PM, Joe Mistachkin wrote: > > Eric Rubin-Smith wrote: > > > > (1) Default allow-symlinks to true > > (2) Fix bug in which the allow-symlinks setting is not honored while > > opening a repository > > > > Please try the latest Fossil trunk and let

Re: [fossil-users] meeting tomorrow at 10:00?

Hi, I posted to the wrong mailing list. I apologize. Serves me right for naming them so similarly (and for not getting enough sleep). You may safely hide/delete/clean up http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg21825.html (as well as this message) as it was not intended

Re: [fossil-users] symlinks (was Re: xkcd on git)

On Tue, Nov 3, 2015 at 2:44 PM, Joe Mistachkin wrote: > > Eric Rubin-Smith wrote: > > > > (2) Fix bug in which the allow-symlinks setting is not honored while > > opening a repository > > > > Did the following changes (a while back) not address this? > >

Re: [fossil-users] symlinks (was Re: xkcd on git)

Eric Rubin-Smith wrote: > > (2) Fix bug in which the allow-symlinks setting is not honored while > opening a repository > Did the following changes (a while back) not address this? https://www.fossil-scm.org/fossil/vinfo/010451e7a5fe116a?sbs=0 If not, in what way are they not adequate?

[fossil-users] [patch] Default skin, show Release Version

Hi, At a quick glance there does not seem any way to determine the Fossil Release Version from the web interface. It seems some skins show the Release Version in the footer, and some do not. I would like to request the default skin to do so as per this trivial patch... @@ -1,6 +1,6 @@

Re: [fossil-users] symlinks (was Re: xkcd on git)

Eric Rubin-Smith wrote: > > Version [aa92270fe9] seems to have regressed the case of opening a repository with a > .fossil-checkout/allow-symlinks file set to 'on'. See the transcript below. Note > that I had created the repository earlier (I assume this does not matter for the > purposes of

Re: [fossil-users] xkcd on git

On Tue, Nov 3, 2015 at 7:59 AM, Michal Suchanek wrote: > > On 2 November 2015 at 20:40, Richard Hipp wrote: > > But on the other hand, you should not be checking-in untested changes. > > The proper way to do incremental check-ins is to stash the whole lot, >

Re: [fossil-users] handling backports

On 3 November 2015 at 15:14, Richard Hipp wrote: > > That is exactly what --cherrypick is for. > > You can see a couple of recent examples of this in the SQLite source > tree, where we took a couple bug fixes from trunk and > cherrypick-merged them into the branch-3.9 branch to

Re: [fossil-users] symlinks (was Re: xkcd on git)

I also find symlinks useful for similar reasons - although I do not use nested repos, so my usage is simpler. It does become a problem when I work with someone who uses Windows and can see that is harder to fix. Would it not be possible for Fossil to detect whether the user can create symlinks

Re: [fossil-users] symlinks (was Re: xkcd on git)

> - Symlinks. Now we're getting into file system specifics. Some users > may want to track them because they find them useful. What about users > that find FIFOs or block devices or character device useful? Should > fossil attempt to save enough information to recreate them? > Support for FIFOs