Re: [darcs-users] so long and thanks for all the darcs

Ben Franksen writes: > Hi Stephen > > Am 08.03.2018 um 09:52 schrieb Stephen J. Turnbull: > > Another long one. But we're converging! > > Indeed. I think we agree on almost every point, I think so, at this point. You added some stuff that I don't disagree with but think I can shed some

Re: [darcs-users] so long and thanks for all the darcs

Another long one. But we're converging! Ben Franksen writes: > Am 05.03.2018 um 04:40 schrieb Stephen J. Turnbull: > > Although git and Mercurial (and Bazaar) share a repository model that > > is somewhat more complex (DAG of versions), only git's implementation > > is faithful with an

Re: [darcs-users] so long and thanks for all the darcs

Am 13.04.2018 um 10:19 schrieb Stephen J. Turnbull: > Benjamin Franksen writes: > > On 04/10/2018 08:34 AM, Stephen J. Turnbull wrote: > > > > Any user who understands what a ref is will say "a Darcs tag is > > > too a ref!" I think. > > > > Perhaps (but you won't, right?). > > I would, in

Re: [darcs-users] so long and thanks for all the darcs

On 04/10/2018 08:34 AM, Stephen J. Turnbull wrote: > Ben Franksen writes: > > Am 29.03.2018 um 10:08 schrieb Stephen J. Turnbull: > > > Internally we do use references, similar to git (we refer to patches, > > inventories, and trees via content hash). But in contrast to git, these > > are not

Re: [darcs-users] so long and thanks for all the darcs

By the way, I found this thread really interesting and informative, and learned some things about git and version control. So thanks for the discussion. Content-addressed storage is pretty interesting. There was actually a filesystem based on this, for Plan 9, called fossil. It was a true

Re: [darcs-users] so long and thanks for all the darcs

Am 29.03.2018 um 10:08 schrieb Stephen J. Turnbull: > Ben Franksen writes: > > If yes, then I begin to understand why as a Darcs user I found it so > > difficult to become familiar with git. Because this concept of a "ref" > > has no (user visible) counterpart in Darcs. It doesn't exist because

Re: [darcs-users] so long and thanks for all the darcs

Ben Franksen writes: > > The refs are supposed to all be copied to refs/remotes/origin, > Hm, that may clarify a few things for me. So a "ref" is a file which > contains a hash that references an object. That's how it's made persistent. However, there are older methods (symlinks, for

Re: [darcs-users] so long and thanks for all the darcs

Hi Steve sorry for (again) responding at length. You gave me yet more ideas... Am 22.03.2018 um 01:15 schrieb Stephen J. Turnbull: > Ben Franksen writes: >> My experience with git tells me that when I make a clone what I get >> is /not/ identical to upstream. > > I may have miswritten. What is

Re: [darcs-users] so long and thanks for all the darcs

Am Donnerstag, den 22.03.2018, 09:12 +0900 schrieb Stephen J. Turnbull: > Wolfgang Jeltsch writes: > > > What about double-clicks, which mark the word (in this case, the > > SHA1 hash) under the cursor? > > The discoverability problem (git repositories normally will have > several dangling

Re: [darcs-users] so long and thanks for all the darcs

On 03/20/2018 10:33 AM, Stephen J. Turnbull wrote: [about git's message "you are in 'detached HEAD' state..."] > > > But to get that message you need to explicitly checkout a commit that > > > is not the target of a branch ref. > > > > A tag, for instance. > > Yes. I guess that a lot of

Re: [darcs-users] so long and thanks for all the darcs

Am 20.03.2018 um 10:33 schrieb Stephen J. Turnbull: > Ben Franksen writes: > > Am 19.03.2018 um 09:12 schrieb Stephen J. Turnbull: > > But git chooses to not clone all the refs by default and there is a > > reason for that because it would have to pull all the referenced > > commits, too, > >

Re: [darcs-users] so long and thanks for all the darcs

Am Dienstag, den 20.03.2018, 18:33 +0900 schrieb Stephen J. Turnbull: > Ben Franksen writes: > > Copy & paste? It's 2018, not the 1970s. > > I frequently drop characters at the beginning or end of a selection > when using touchpads or handhelds, and occasionally with a mouse. What about

Re: [darcs-users] so long and thanks for all the darcs

Ben Franksen writes: > Am 19.03.2018 um 09:12 schrieb Stephen J. Turnbull: > > I don't think this is possible with raw git on a remote repository. I > > believe you need to fetch all the remote refs, and query locally. > > In Darcs we have to query the remote repo anyway. You don't want to

Re: [darcs-users] so long and thanks for all the darcs

Am 05.03.2018 um 04:40 schrieb Stephen J. Turnbull: > Executive summary: > > Darcs is an elegant system with a very simple underlying repository > model (set of patches) and an implementation that is faithful to that > model. This makes Darcs easy to understand and use. > > Although git and

Re: [darcs-users] so long and thanks for all the darcs

On Mon, Mar 5, 2018 at 2:08 AM, Ben Franksen wrote: > I have just tried this and in fact when I resume the edit all the escape > sequences are printed literally. However, the editor does react to them: > I can quit using ":q" and the garbage on the screen isn't actually

Re: [darcs-users] so long and thanks for all the darcs

Am 05.03.2018 um 10:19 schrieb Ben Franksen: > Am 05.03.2018 um 03:40 schrieb Evan Laforge: >> Record changes in darcs 2.12.5, then say yes to "add a long comment" >> where EDITOR=vim. Now ^Z out of vim, and then fg back. At that >> point, vim is in command mode, but any keys just appear

Re: [darcs-users] so long and thanks for all the darcs

On Mon, Mar 5, 2018 at 1:19 AM, Ben Franksen wrote: > But you /can/ work in the same way with darcs: just don't (q)uit, rather > say (d)one. Then use 'darcs amend' to add more changes or 'darcs amend > --unrecord' to remove changes. There is also the --edit-long-comment >

Re: [darcs-users] so long and thanks for all the darcs

Am 05.03.2018 um 01:47 schrieb Karl O. Pinc: > On Sun, 4 Mar 2018 23:23:33 +0100 > Ben Franksen wrote: > >> What made me re-consider >> the idea was that I found I like the way mercurial automatically >> creates a branch when you pull a conflicting patch. > >> But >>

Re: [darcs-users] so long and thanks for all the darcs

Am 05.03.2018 um 03:40 schrieb Evan Laforge: > On Sun, Mar 4, 2018 at 2:46 AM, Ben Franksen wrote: >>> There are a few other quibbles, like how obliterate -O is too slow to >>> be useful, >> >> (perhaps we should have made --no-minimize the default?) > > Is that what you

Re: [darcs-users] so long and thanks for all the darcs

On Sun, Mar 4, 2018 at 2:46 AM, Ben Franksen wrote: >> There are a few other quibbles, like how obliterate -O is too slow to >> be useful, > > (perhaps we should have made --no-minimize the default?) Is that what you get when you ^C while it's working? If so, yeah I'd

Re: [darcs-users] so long and thanks for all the darcs

On Sun, 4 Mar 2018 23:23:33 +0100 Ben Franksen wrote: > What made me re-consider > the idea was that I found I like the way mercurial automatically > creates a branch when you pull a conflicting patch. > But > when you look at it from a darcs viewpoint, automatically

Re: [darcs-users] so long and thanks for all the darcs

Am 04.03.2018 um 21:12 schrieb Karl O. Pinc: > On Sun, 4 Mar 2018 12:04:01 +0100 > Stephane Bortzmeyer wrote: > >> * no branches. Don't add them! The one-branch-per-repo model is much >> better > > Thinking out loud here. > > If I had to vote today I'd say: > > -1 on

Re: [darcs-users] so long and thanks for all the darcs

On Sat, Mar 03, 2018 at 05:54:48PM -0800, Evan Laforge wrote a message of 45 lines which said: > I recently switched my main project from darcs to git. > > I'm mentioning it because I feel like it might be one of the larger > and older darcs repos out there, with the

Re: [darcs-users] so long and thanks for all the darcs

Am 04.03.2018 um 05:03 schrieb Karl O. Pinc: > On Sat, 3 Mar 2018 18:36:32 -0800 > Evan Laforge wrote: > >> On Sat, Mar 3, 2018 at 6:26 PM, Karl O. Pinc wrote: >>> This being so, I'm curious why a darcs user would choose >>> git over mercurial. >> >>

Re: [darcs-users] so long and thanks for all the darcs

On Sat, 3 Mar 2018 18:36:32 -0800 Evan Laforge wrote: > On Sat, Mar 3, 2018 at 6:26 PM, Karl O. Pinc wrote: > > This being so, I'm curious why a darcs user would choose > > git over mercurial. > > Honestly, because I don't know mercurial. I should fix that

Re: [darcs-users] so long and thanks for all the darcs

On Sat, Mar 3, 2018 at 6:26 PM, Karl O. Pinc wrote: > I use darcs, git, and mercurial; git only > for non-technical reasons. I'm pretty much on-board > with the git critique of: > https://stevebennett.me/2012/02/24/10-things-i-hate-about-git/ Can't say I disagree much with that