Re: [fossil-users] Unexpected merge conflict

On Nov 13, 2015 8:20 AM, "Tony Papadimitriou" wrote: > > Here’s a merge conflict I thought should have been resolved automatically: > > I have the trunk version from where the symbol RF_OUT is renamed to SRF_OUT in the branch version. It has never been renamed to SRF_OUT in the

Re: [fossil-users] Unexpected merge conflict

tent carries previous > check-ins” or “Cannot cherry pick this particular line” would also be nice. > > *From:* Scott Robison <sc...@casaderobison.com> > *Sent:* Friday, November 13, 2015 6:40 PM > *To:* Fossil SCM user's discussion <fossil-users@lists.fossil-scm

Re: [fossil-users] source code file is considered by fossil to be binary.

ors. Certainly isn't "Unicode compliant" since Unicode doesn't assign glyphs to those code points, but it does display them. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] source code file is considered by fossil to be binary.

me up with some sort of quoting escape mechanism to show such characters, but it would be non-standard by definition. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] source code file is considered by fossil to be binary.

aracter codes less than ASCII SPACE? CR, LF, TAB all have well defined meanings. How should the rest be rendered? -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] xkcd on git

t my choice. It was the choice of someone else and it had a negative impact on me. I was able to fix it be deleting my local repo and recloning, so it wasn't the end of the world, but I have a hard time imagining a scenario where fossil would have allowed somethin

Re: [fossil-users] xkcd on git

po maintenance / usage would not make that possible. Or maybe it would. I'd love to hear some example of how that might happen in fossil. It's one thing to be actively using a repository and using the full set of repo management commands (open, update, commit, branch, etc) and getting into some

Re: [fossil-users] xkcd on git

my employer has been migrating to git from svn for a while now, though we're not 100% migrated yet), I find it maddening. I have used fossil on some projects and wind up committing the "final product" to git when necessary (since git fans seem to find intermediate history objectionable or of li

Re: [fossil-users] xkcd on git

On Mon, Nov 2, 2015 at 5:01 PM, Ron W <ronw.m...@gmail.com> wrote: > On Mon, Nov 2, 2015 at 6:38 PM, Scott Robison <sc...@casaderobison.com> > wrote: >> >> From https://en.wikipedia.org/wiki/NTFS_symbolic_link#Restrictions: The >> default security settings

Re: [fossil-users] xkcd on git

ing symbolic links. *This behavior can be changed running "secpol.msc" the Local Security Policy management console (under: Security Settings\Local Policies\User Rights Assignment\Create symbolic links). It can be worked around by starting **cmd.exe <https://en.wikipedia.org/wiki/Cmd.

Re: [fossil-users] xkcd on git

On Mon, Nov 2, 2015 at 5:21 PM, Jan Danielsson <jan.m.daniels...@gmail.com> wrote: > On 03/11/15 00:38, Scott Robison wrote: > >>> On 11/2/15, Jan Danielsson <jan.m.daniels...@gmail.com> wrote: > >>>> > >>>> Supporting symlinks on Windows

Re: [fossil-users] xkcd on git

On Nov 1, 2015 6:09 PM, "Ron W" wrote: > > On Sun, Nov 1, 2015 at 4:14 AM, Stephan Beal wrote: >> >> But if it only stores a pointer, and requires the user to reconstruct the link, it's not terribly useful/friendly. The user would potentially have to

Re: [fossil-users] SHA1 and security

On Oct 29, 2015 6:50 PM, "Warren Young" wrote: > > I also wonder what will happen if someone with an existing checkout checks in a diff against the changeling file, and the diffs overlap with the evil bits. I assume the server will try to apply the patch and fail, or the next

Re: [fossil-users] SHA-1 in user.pw field

y encryption to the data so that the operating system only decrypts data on demand. This isn't perfect, and unfortunately, the point to a DVCS is to share the data with anyone who has access (assuming the access is permitted and not fraudulently obtained). Encrypting the data isn't really an option

Re: [fossil-users] SHA1 and security

On Thu, Oct 29, 2015 at 8:41 AM, Eduard <eduard.c.dumitre...@gmail.com> wrote: > Hi Scott, > > Thank you for your reply! > > On 10/29/2015 01:40 AM, Scott Robison wrote: > > On Wed, Oct 28, 2015 at 6:37 PM, Eduard <eduard.c.dumitre...@gmail.com > > <mailt

Re: [fossil-users] SHA1 and security

all files > in the R card. It's an MD5 hash, but that still means the attacker > would have to find replacement source code that (a) matched both SHA1 > and MD5 hashes and (b) was valid C code. Good luck with that. > Wait, so fossil is already doing what I suggested it could

Re: [fossil-users] SHA1 and security

On Thu, Oct 29, 2015 at 1:07 PM, Warren Young <w...@etr-usa.com> wrote: > On Oct 28, 2015, at 11:40 PM, Scott Robison <sc...@casaderobison.com> > wrote: > > the odds of a non-malicious collision are so close to zero that those > odds might as well be zero. > &g

Re: [fossil-users] SHA1 and security

ing man in the middle attack" or "capable of social engineering to convince people to use evil artifact" or "something else I can't think of at the moment") seems to be a pretty tiny intersection. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] SHA1 and security

I can see the point. In this case, it's just an identifier, and the odds of a non-malicious collision are so close to zero that those odds might as well be zero. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.

Re: [fossil-users] The "exec-rel-paths" branch...

> -- > Joe Mistachkin > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fo

Re: [fossil-users] Attack against the Fossil website?

___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Attack against the Fossil website?

> Is this anything to be concerned about? Should I block this anomalous > traffic, or should I just leave them alone? > I found this link that might explain what you're seeing: http://resources.distilnetworks.com/h/i/53822092-is-pushdo-screwing-you-details-of-the-botnet/181642 -- Scott Robison __

Re: [fossil-users] MERGE problem (with renames/deletes)

newly introduced (or re-introduced) file should be merged because > it is wanted change.* > > Thanks. > > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman

Re: [fossil-users] MERGE problem (with renames/deletes)

rted after renaming file in a branch, > >> merging trunk changes to it works only once, and subsequent merges > >> do nothing: > >> > >> > http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg20758.html > ‎ > > > I'm not sure what to do

Re: [fossil-users] MERGE problem (with renames/deletes)

ossil-users%40lists.fossil-scm.org/msg20417.html > > > > 2. ‎(In June) Andy G reported after renaming file in a branch, merging > trunk changes to it works only once, and subsequent merges do nothing: > > > http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg20758.html &

Re: [fossil-users] MERGE problem

list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Why Hash

On Sep 16, 2015 3:24 AM, "Michal Suchanek" <hramr...@gmail.com> wrote: > > On 16 September 2015 at 05:16, Scott Robison <sc...@casaderobison.com> wrote: > > But GPG could solve any weaknesses with Fossil's use of SHA-1, though. It > > won't prevent a det

[fossil-users] Interesting video on Google repository

https://www.youtube.com/watch?v=W71BTkUbdqE -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Why Hash

eliberate collisions, but even in so doing there is far more to do than just "push an update". Given the widespread use of SHA-1 in DVCS systems, and the use of GPG signatures to authenticate commits, I think it would be reasonable to enhance the cryptographic security in a future vers

Re: [fossil-users] Why Hash

On Tue, Sep 15, 2015 at 7:46 PM, Warren Young <w...@etr-usa.com> wrote: > On Sep 15, 2015, at 7:01 PM, Scott Robison <sc...@casaderobison.com> > wrote: > > > > I think calling it a non sequitur is not completely fair > > Stephan stated that Fossil isn’t

Re: [fossil-users] Why Hash

owers that be want to make a change of algorithm for ID generation, that'd be fine. I just don't see any urgency myself in non-cryptographic applications. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Why Hash

On Mon, Sep 14, 2015 at 1:01 PM, Warren Young <w...@etr-usa.com> wrote: > On Sep 14, 2015, at 12:11 PM, Scott Robison <sc...@casaderobison.com> > wrote: > > > > > Fossil would be free to switch to a different algorithm later if that > seemed like a good id

Re: [fossil-users] diff after update

ecame a > feature of ``fossil undo?'' > > fossil undo --diff > Ooh, I like this... +1 I also like fossil diff --undo, but if that is too confusing, perhaps fossil diff --undo-buffer Or other word for buffer. -- Scott Robison ___ fossil-users maili

Re: [fossil-users] diff after update

ossil stash gdiff ?STASHID? Why not do it the same way for undo? It seems to be most in line with precedent. Perhaps because undo doesn't currently have subcommands, just options. Still, it would be the most intuitive thing based on existing practice. -- Scott Robison __

[fossil-users] Bad press for GitHub

Not really a flaw with git, but this jumped out at me tonight: http://www.theregister.co.uk/2015/09/01/github_bug_costs_man_thousands/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] Bad press for GitHub

at self hosting is arguably safer (at least from this sort of attack) than using something like GitHub (or Chisel which doesn't even rate a mention on the Wikipedia page referenced). And I (still) feel bad for the guy. I hope GitHub or Microsoft help reimburse him, at least in part. SDR > >

Re: [fossil-users] Bad press for GitHub

d repositories are arguably safer. Especially projects no one has ever heard of! ;) Perhaps the first time in history someone was sad that git didn't lose data. #zing > > > On Wed, Sep 2, 2015 at 10:39 AM, Stephan Beal <sgb...@googlemail.com> wrote: >> >> On Wed, Sep 2, 2

Re: [fossil-users] fossil all rebuild: “not a valid repository”

question, or am telling you stuff you already know, my apologies. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Any interest in testing/merging check-in-edit branch?

On phone, apologies for top posting. To me amend uuid should behave as much as possible like commit, though I can appreciate that some might disagree. On Jul 17, 2015 8:38 PM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Sergei Gavrikov on Thu, 16 Jul 2015 17:21:55 +0300: I also

Re: [fossil-users] Remove redundant shun links from doc page.

://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Feature idea: Protected branches

are hesitant to try to implement something like this. If fossil were a CVCS like svn (or could be configured for a similar use case), it would be easier to enforce these types of permissions. -- Scott Robison ___ fossil-users mailing list fossil-users

Re: [fossil-users] Feature idea: Protected branches

On Tue, May 12, 2015 at 9:27 PM, Warren Young w...@etr-usa.com wrote: On May 12, 2015, at 5:51 PM, Scott Robison sc...@casaderobison.com wrote: the difficult part comes in the sync, since they only deal with artifacts. Once someone clones the repo, they have full access to that copy to do

Re: [fossil-users] FOSSIL STASH wish list

On Apr 30, 2015 8:21 AM, to...@acm.org wrote: To add to the perpetual wish list: Can the STASH [SAVE] command be made to behave similarly to the COMMIT command with respect to comments in the editor? That is, if nothing is typed as stash comments, the stash operation to be aborted. It

Re: [fossil-users] Limiting HTTP/1.1 host

On Thu, Apr 30, 2015 at 1:27 PM, Ron W ronw.m...@gmail.com wrote: On Thu, Apr 30, 2015 at 2:57 PM, Scott Robison sc...@casaderobison.com wrote: In any case, if they are looking for a machine to exploit, and they request a page from http://1.2.3.4/; instead of http://www.legitimate

Re: [fossil-users] Limiting HTTP/1.1 host

://1.2.3.4/; instead of http://www.legitimate-domain.com/;, simply dropping the connection could be an effective mitigation strategy. A typical 404 response might include all the information the bad actor needs. Why make their job any easier? -- Scott Robison

Re: [fossil-users] Two trunks?

. leaves by default only shows open leaves, but has --all and --closed options to pick other sets of leaves that might be useful, as well as --recompute. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil

Re: [fossil-users] terminology confusion

in this position seven years down the road. Or we just continue to document what we mean when we use the term fork (perhaps providing the extra text two leaves on the same branch or some such when a fork warning is generated) and continue to provide the existing tools to merge or rename. -- Scott Robison

Re: [fossil-users] terminology confusion

On Thu, Apr 16, 2015 at 2:58 PM, Ron W ronw.m...@gmail.com wrote: On Thu, Apr 16, 2015 at 4:30 PM, Scott Robison sc...@casaderobison.com wrote: Some thoughts: More seriously, the Wikipedia article on forking is probably worth a read: http://en.wikipedia.org/wiki/Fork_(software_development

Re: [fossil-users] Merge - including files from other branches - best practice?

On Thu, Apr 16, 2015 at 8:15 PM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Scott Robison on Thu, 16 Apr 2015 16:36:59 -0600: It is by design. Merging isn't always intuitive, and certainly there could be a bug in it. Perhaps like this one: http://fossil.bradfords.org:8080

Re: [fossil-users] Merging deleted files (Was: Merge - including files from other branches - best practice?)

bucks. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Merge - including files from other branches - best practice?

/fossil-users -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Symlink trouble

On Wed, Apr 8, 2015 at 12:17 PM, Ron W ronw.m...@gmail.com wrote: On Wed, Apr 8, 2015 at 1:58 PM, Scott Robison sc...@casaderobison.com wrote: Or whatever your team dictates. :) In our case, we are required to follow industry guidelines, except where compelling technical issues require

Re: [fossil-users] Symlink trouble

), use what you have to use for the platform. Otherwise use whatever you feel most comfortable with. Or whatever your team dictates. :) -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi

Re: [fossil-users] Is this a crazy idea?

On Mar 20, 2015 1:07 PM, Abilio Marques abili...@gmail.com wrote: Yeah, stash is the way I do all the time, but sometimes I want to exclude binaries that are regenerated each time a change and compilation occurs, until I'm ready to the new version to go into trunk. Top of my mind, the PDF

Re: [fossil-users] Select specific changes within files

there are third party components included. +1 -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Select specific changes within files

want until you're satisfied. With fossil, this doesn't work. Except that it can work in a similarly functional way (yet less confusing from my perspective) as I outlined in my previous email. -- Scott Robison ___ fossil-users mailing list fossil-users

Re: [fossil-users] Select specific changes within files

improvements, but I personally can't see where the git partial file commit functionality buys you anything you can't just as effectively do with a text editor and existing support from fossil, and with far less confusion or complexity. -- Scott Robison ___ fossil

Re: [fossil-users] Is this a crazy idea?

On Thu, Mar 19, 2015 at 6:32 PM, Richard Hipp d...@sqlite.org wrote: On 3/19/15, Scott Robison sc...@casaderobison.com wrote: I can't answer for Abilio, but given my recent increased experience with git due to workplace changes: the git folk seem to prefer the staging area because

Re: [fossil-users] Is this a crazy idea?

they very well may be working on multiple branches at the same time in the same tree. See this: http://stackoverflow.com/questions/6270193/multiple-working-directories-with-git The staging area can be disabled / skipped, but that's how it has been explained to me. -- Scott Robison

Re: [fossil-users] home directory must be writeable

. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Possible Bug in Merge Conflict Blocks

is that I understand the merging code and rationale a lot better now than I did 24 hours ago. :) -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Possible Bug in Merge Conflict Blocks

ANCESTER MERGED IN blocks. Instead it is showing the all except for the final line. Just FYI. I can try to take a look at it later, but given the speed that these things are often fixed, I figured I'd report it now. -- Scott Robison ___ fossil-users

Re: [fossil-users] Possible Bug in Merge Conflict Blocks

On Wed, Mar 18, 2015 at 11:42 AM, Richard Hipp d...@sqlite.org wrote: On 3/18/15, Scott Robison sc...@casaderobison.com wrote: Just FYI. I can try to take a look at it later, but given the speed that these things are often fixed, I figured I'd report it now. Too many balls in flight

Re: [fossil-users] Possible Bug in Merge Conflict Blocks

. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Possible Bug in Merge Conflict Blocks

this in src/file.c. Or at least I was. It was a perfect storm. Confusing changes between trunk branch some sleep deprivation experiment my body is forcing me into took me a while to come to the realization I shared above. -- Scott Robison ___ fossil

Re: [fossil-users] Git-v-Fossil. Was: Google code shutting down

On Mar 16, 2015 9:44 AM, James Moger james.mo...@gmail.com wrote: On Fri, Mar 13, 2015 at 8:26 PM, Richard Hipp d...@sqlite.org wrote: Fossil was created to support the development of SQLite. All other use (and there is more and more of that lately) is just gravy. They all start

Re: [fossil-users] Google code shutting down

while disconnected even if actual code banging was not in progress. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] what determines the string length of sha1 display in the timeline?

whatsoever. It is less than 0.02% of the total possible sha1 hashes, so I'm not worried about it personally. Just throwing it out there for consideration. :) -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http

Re: [fossil-users] Repo with many initial commits + more wish list

. :) -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] FLOSS interview

Just watched the interview at http://twit.tv/show/floss-weekly/320 ... good job! I can't believe DRH didn't drop my name, but I'll forgive him this time. {snicker} Oh, and I'm always looking for a good text editor. Show us what you've got! :) -- Scott Robison

Re: [fossil-users] Hungarian Notation Used in Fossil

On Dec 17, 2014 8:26 AM, Ron W ronw.m...@gmail.com wrote: On Wed, Dec 17, 2014 at 2:10 AM, Scott Robison sc...@casaderobison.com wrote: The thing I dislike about the strict Microsoft way is the embedding of actual type data into the variable name, so that if you decide to change a type later

Re: [fossil-users] Hungarian Notation Used in Fossil

On Wed, Dec 17, 2014 at 11:35 AM, Warren Young w...@etr-usa.com wrote: On Dec 17, 2014, at 12:10 AM, Scott Robison sc...@casaderobison.com wrote: I loathe ... uh ... do not care for ... the embedding of scope or constness. g is easy to justify. It’s a heads-up to the programmer: “Pay

Re: [fossil-users] Hungarian Notation Used in Fossil

. Of course it's sane! :) -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] http --enforce-remote-user

On Oct 13, 2014 7:42 AM, David Mason dma...@ryerson.ca wrote: On 13 October 2014 04:54, Tony Papadimitriou to...@acm.org wrote: The claim that once you shun a 0-length file you will not be able to commit another 0-length file again is not entirely true. If you first delete the existing

Re: [fossil-users] Tip: abusing autosync to abort a commit

On Oct 6, 2014 12:26 PM, Stephan Beal sgb...@googlemail.com wrote: Hi, all, (This just happened...) The autosync option provides (incidentally, not specifically by design) a feature one doesn't have if it is turned off: the ability to abort a commit within a small (and unknown/varying) time

Re: [fossil-users] Tip: abusing autosync to abort a commit

Bah! Commit not conmit. Stupid phone keyboard. On Oct 6, 2014 12:39 PM, Scott Robison sc...@casaderobison.com wrote: On Oct 6, 2014 12:26 PM, Stephan Beal sgb...@googlemail.com wrote: Hi, all, (This just happened...) The autosync option provides (incidentally, not specifically

Re: [fossil-users] Tip: abusing autosync to abort a commit

I just wanted to give you a little grief based on past -m comments. :) On Oct 6, 2014 12:42 PM, Stephan Beal sgb...@googlemail.com wrote: On Mon, Oct 6, 2014 at 8:39 PM, Scott Robison sc...@casaderobison.com wrote: I have that functionality without auto sync. I don't use the -m comment

Re: [fossil-users] Tip: abusing autosync to abort a commit

as a TA for the class I dealt with a few students who had the same problem. Students were more apt to blame me (even though there was nothing I could have done about it). :) Anyway... yeah. Not all safety systems are very safe. :) -- Scott Robison

Re: [fossil-users] Proposed improvement to inheritedprivilegessubscripts.

On Sep 30, 2014 9:57 AM, Stephan Beal sgb...@googlemail.com wrote: On Tue, Sep 30, 2014 at 5:54 PM, Andy Bradford amb-fos...@bradfords.org wrote: I actually did try to update it myself last night but had alignment issues due to the font on the (s) letter not being a fixed font. i

Re: [fossil-users] Proposed improvement to inheritedprivilegessubscripts.

On Sep 28, 2014 12:49 AM, Stephan Beal sgb...@googlemail.com wrote: Sidenote: i'm curious why most people prefer postscript addition, when prefix is never slower and sometimes faster. (Not that it matters one iota for a case like this, it just seems to be very deeply embedded in most people i

Re: [fossil-users] security notice for _potential_ problem with _some_ CGI-hosted repos

Basic secured site (so now script access until after authentication, and I am the only one with a username/password, at least for now). I'm not too worried about it, but it's good to know that I probably need to go do security updates on my server. -- Scott Robison

Re: [fossil-users] fossil for web site maintenance [was how to use git to lose data]

On Sat, Sep 6, 2014 at 9:52 AM, Miles Fidelman mfidel...@meetinghouse.net wrote: Scott Robison wrote: ... One of my newest uses for fossil is the one case in which I'm using it distributed (even though all by myself): My blog (such as it is). It is not a unique idea at all, but I finally

Re: [fossil-users] how to use git to lose data

fragile to some people while fossil seems inflexible to others. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] More on Fossil-v-Git

FYI the Google translation service is reporting that the site is compromised in some way. So no translation at the moment, and I would probably advise extreme caution loading the original site even of you can read Russian. Sorry for top post, sent from phone. SDR On Sep 5, 2014 5:52 AM, Richard

Re: [fossil-users] how to use git to lose data

server and update the live site, making the generated file tree available (and giving me a live backup of all the files). -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman

Re: [fossil-users] how to use git to lose data

On Sep 2, 2014 12:10 PM, Ron W ronw.m...@gmail.com wrote: On Mon, Sep 1, 2014 at 5:49 PM, Scott Robison sc...@casaderobison.com wrote: It certainly wouldn't work in the same way git is used by the linux kernel team. Git was originally created by the Linux Kernel team, including Linus. It's

Re: [fossil-users] how to use git to lose data

where large / deep hierarchies of collaborators are at work, fossil is probably not an ideal solution. It certainly wouldn't work in the same way git is used by the linux kernel team. I'll be interested to hear back from him what he thinks. -- Scott Robison

Re: [fossil-users] symlinks

it is not)? -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] symlinks

On Thu, Aug 28, 2014 at 9:26 AM, Richard Hipp d...@sqlite.org wrote: On Thu, Aug 28, 2014 at 11:23 AM, Scott Robison sc...@casaderobison.com wrote: On Thu, Aug 28, 2014 at 9:04 AM, Richard Hipp d...@sqlite.org wrote: D'oh. I had searched the forum + google and found threads in which

Re: [fossil-users] symlinks

On Thu, Aug 28, 2014 at 9:26 AM, Richard Hipp d...@sqlite.org wrote: On Thu, Aug 28, 2014 at 11:23 AM, Scott Robison sc...@casaderobison.com wrote: On Thu, Aug 28, 2014 at 9:04 AM, Richard Hipp d...@sqlite.org wrote: D'oh. I had searched the forum + google and found threads in which

[fossil-users] Versionable settings question

reasoning as to why? -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Closing fossil output

On Mon, Aug 11, 2014 at 1:33 PM, Alysson Gonçalves de Azevedo agalys...@gmail.com wrote: Well, I don't really get, a closed file descriptor wouldn't cause corruption, would? btw, i'll use /dev/null. It wouldn't cause corruption in and of itself, but once you close a file descriptor, it

Re: [fossil-users] Closing fossil output

On Mon, Aug 11, 2014 at 2:36 PM, Alysson Gonçalves de Azevedo agalys...@gmail.com wrote: I understand why one cannot open a database (or any other command) from descriptor file minor than 3. But why this `fossil branch 21` do work and `fossil branch 2-` doesn't, it's not clear. If i open a

Re: [fossil-users] fossil vs git-based arrangements. code review and ticket export

, relying on luck to find good people willing to work for sub-market wages. We found some, but it was an exhausting process. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman

Re: [fossil-users] Unusual timeline

On Wed, Jul 9, 2014 at 5:49 PM, Andy Goth andrew.m.g...@gmail.com wrote: http://fossil-scm.org/index.html/timeline?p=92c2c1e5e18b19c5b05ea5684feb0bbeeb6670fd What's going on here? Everything is tagged trunk, yet [b4a53ba45f] is displayed as if on a branch. Was there a fork or something?

Re: [fossil-users] File contains invalid UTF-8, but is not UTF-8.

be an extended ASCII character from one of the ISO-8859-X code pages. Or it could be real binary data that just happens to mostly have ASCII text in it. I think the best idea is to encode these special characters as escaped sequences whenever possible. -- Scott Robison

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

On Jun 17, 2014 8:42 AM, Eric Rubin-Smith eas@gmail.com wrote: This thread is hilarious. I thought I was pretty old-school -- I use vi, xterm, fvwm2, and other tools written by my forebears around the time when I was born. I get made fun of by people twice my age for my dev toolkit.

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

On Mon, Jun 16, 2014 at 2:24 PM, Stephan Beal sgb...@googlemail.com wrote: Hi, all, This is for Unix-shell users only (including workalikes on Windows)... Here's a time-saving tip which i use very often myself, but most CLI users i know don't seem to know about: It often happens that i'm

Re: [fossil-users] autosync from GUI

On Jun 7, 2014 1:27 PM, Ron Wilson ronw.m...@gmail.com wrote: On Sat, Jun 7, 2014 at 2:23 PM, Stephan Beal sgb...@googlemail.com wrote: For the local UI case, sure, i can see it being useful, but people would also expect it to work remotely, and it often wouldn't. When running the local UI,

Re: [fossil-users] autocrlf like in Git?

On Jun 7, 2014 1:47 PM, to...@acm.org wrote: Well, I can give a couple of personal examples that you easily try yourselves: * Windows side: Copy/Paste in Windows can not deal with LF endings correctly. Example: PNotepad editor in Windows loads Linux files but copy-pasting from it (for

<    1   2   3   >