[fossil-users] Fwd: Re: Conversation with a CM guy

Forwarding to list for further discussion, mail was sent to me privately though I can't see why. Must have been inadvertent. Forwarded Message Subject: Re: [fossil-users] Conversation with a CM guy Date: Mon, 16 May 2016 15:34:02 -0400 From: John P. Rouillard

Re: [fossil-users] Repairing trunk/timeline after a shun

On 5/16/2016 8:00 PM, Richard Hipp wrote: > On 5/16/16, Andy Goth wrote: >> I've wanted reparenting capability to support importing old history into >> a Fossil repository. > > I interpret your sentence above as "I volunteer to test out the new > code!". Thanks! I

Re: [fossil-users] Conversation with a CM guy

On 5/16/2016 11:24 PM, Stephan Beal wrote: > It overwrote the whole drive with the word Hello. Or at least the first block, which is arguably the most important one since it tends to contain tables critical to being able to actually find anything. -- Andy Goth | signature.asc Description:

Re: [fossil-users] Repairing trunk/timeline after a shun

On 5/14/2016 4:59 PM, John P. Rouillard wrote: > fossil init shun.fossil > mkdir shun > cd shun > fossil open ../shun.fossil > echo 2 > 2 > fossil addremove > fossil ci -m "initial commit" > echo 2a > 2 > fossil ci -m "second commit" > echo 2b > 2 > fossil ci -m "third commit" > echo 2shun > 2 >

Re: [fossil-users] Conversation with a CM guy

It overwrote the whole drive with the word Hello. - stephan (Sent from a mobile device, possibly from bed. Please excuse brevity, typos, and top-posting.) On May 17, 2016 06:11, "Arnel" wrote: > On Mon, 16 May 2016 14:39:11 -0400, Richard Hipp wrote: > > 1985. I was

Re: [fossil-users] Conversation with a CM guy

On Mon, 16 May 2016 14:39:11 -0400, Richard Hipp wrote: > 1985. I was working at Bell Labs writing horizontal microcode for a > signal processing chip. Development was hosted on a VAX. There were > about a dozen developers all on the same machine. > > I noticed that the disk drive block

Re: [fossil-users] Conversation with a CM guy

On 5/16/2016 1:17 PM, Andy Goth wrote: > He said he thinks he'll go with Git instead because that would give the > engineers working under him more forward mobility when they eventually > move on to other companies, whereas Fossil is unknown and would not > improve their employability. > > [...] >

Re: [fossil-users] Repairing trunk/timeline after a shun

On 5/16/16, Andy Goth wrote: > > I've wanted reparenting capability to support importing old history into > a Fossil repository. > I interpret your sentence above as "I volunteer to test out the new code!". Thanks! I added a "fossil reparent" command on the "reparent"

Re: [fossil-users] No progress on "fossil cp"

>> Not that this is much consolation to you, Warren, or anyone else that ever >> had to deal with this, but the merge issue will be fixed in the next release >> (or now if you compile your own Fossil binary): > Thank you, drh! And thanks to Joel for taking on this long-lasting and annoying

Re: [fossil-users] No progress on "fossil cp"

On May 16, 2016, at 4:37 PM, Joel Bruick wrote: > > j. van den hoff wrote: >> On Mon, 16 May 2016 19:02:17 +0200, Warren Young wrote: >> >>> 2. If you attempt to merge a change between branches where one of the >>> changed files was renamed after the

Re: [fossil-users] No progress on "fossil cp"

j. van den hoff wrote: On Mon, 16 May 2016 19:02:17 +0200, Warren Young wrote: 1. f finfo can’t trace file history back through a rename. The web version of this (f ui > Files > Ancestry) does manage to report the rename, but it doesn’t trace history back through that

Re: [fossil-users] No progress on "fossil cp"

On Mon, 16 May 2016 19:02:17 +0200, Warren Young wrote: 1. f finfo can’t trace file history back through a rename. The web version of this (f ui > Files > Ancestry) does manage to report the rename, but it doesn’t trace history back through that link to the old name.

Re: [fossil-users] No progress on "fossil cp"

On 5/16/16, Ross Berteig wrote: > >>> That would require a backwards-incompatible change to the manifest format > > Unless some clever trick can be invented that will let older versions of > fossil simply see such files as newly added at the time of the copy > while letting

Re: [fossil-users] No progress on "fossil cp"

On May 16, 2016, at 2:48 PM, Ross Berteig wrote: > > On 5/16/2016 9:53 AM, Warren Young wrote: >> On May 14, 2016, at 4:35 AM, Stephan Beal wrote: >>> But in svn, now that i think about it, cp is, in practice, only used for >>> branching. >> ... >>

Re: [fossil-users] No progress on "fossil cp"

On 5/16/2016 9:53 AM, Warren Young wrote: On May 14, 2016, at 4:35 AM, Stephan Beal wrote: But in svn, now that i think about it, cp is, in practice, only used for branching. ... If the SCM doesn’t remember that y.cpp was cloned from x.cpp Actually, a copy

Re: [fossil-users] Conversation with a CM guy

On May 16, 2016, at 12:17 PM, Andy Goth wrote: > > He also said he likes Git's rebase capability Ask him if the company keeps its books on a whiteboard. If so, git may be a great fit for that company. ;) ___ fossil-users

Re: [fossil-users] Conversation with a CM guy

me personally, if a potential employer wanted me to be a git guru, I wouldn’t take the job. git gives me headaches beyond anything very simple, which as you said, can be learned in a day. Git was one of the worst things to happen to the world of software engineering. What makes git useful is

Re: [fossil-users] Conversation with a CM guy

> > employability. It takes less than a day to pick up git if you're used to fossil. So I don't really think it makes a huge difference as to future employability unless the hiring manager is looking for the wrong things. I grant that most hiring managers *do* look for the wrong things, but

Re: [fossil-users] Conversation with a CM guy

On 5/16/16, Stephan Beal wrote: > > The web UI offers a "delete branch" > feature and i'm always _so tempted_ to click it (and click "yes" on the > subsequent confirmation dialog), _simply to prove a point_. 1985. I was working at Bell Labs writing horizontal microcode

Re: [fossil-users] Conversation with a CM guy

On Mon, May 16, 2016 at 8:17 PM, Andy Goth wrote: > I also told him about the Git issues I've read about, particularly how > fast and loose it plays with preserving history, how branches aren't > much more than tags identifying the final product of a development >

[fossil-users] Conversation with a CM guy

Today I had a conversation with the guy who handles the configuration management for the software project to which I'm on loan. He mentioned that in a couple years he wants to switch away from the old version of Subversion they're currently saddled with. I suggested he consider Fossil since I

Re: [fossil-users] Repairing trunk/timeline after a shun

On 5/16/2016 11:41 AM, John P. Rouillard wrote: > Richard Hipp writes: >> On 5/15/16, Andy Goth wrote: >>> >>> To fix, you're going to have to go back to the version prior to the shun >>> and redo every check-in since that point. >> >> Another option is to "reparent" the

Re: [fossil-users] Unrecognized command-line option, or missing argument: --https

On May 14, 2016, at 7:08 AM, Piotr Orzechowski wrote: > > You solution seems to work with single repo only. There are two easy ways to extend it to multiple repos: 1. Point “fossil serve” in the fslsrv wrapper at a directory of *.fossil files, not at a single

Re: [fossil-users] No progress on "fossil cp"

On May 14, 2016, at 4:11 AM, Stephan Beal wrote: > Fossil does have an 'mv' command which does retain history. Kind of. f mv breaks anything that’s keyed off the file name, since files in Fossil are identified by their path within the repo. I’ve run into two main

Re: [fossil-users] No progress on "fossil cp"

On May 14, 2016, at 4:35 AM, Stephan Beal wrote: > > But in svn, now that i think about it, cp is, in practice, only used for > branching. No, not “only.” For example, I have a small repo containing a bunch of test programs. They’re all very similar, sharing perhaps

Re: [fossil-users] Repairing trunk/timeline after a shun

Hello Richard: In message