From: Junio C Hamano <firstname.lastname@example.org> To: Philip Oakley <email@example.com> Cc: Thomas Gummerer <firstname.lastname@example.org>, Duy Nguyen <email@example.com>, Git Mailing List <firstname.lastname@example.org>, Jonathan Nieder <email@example.com>, Elijah Newren <firstname.lastname@example.org> Subject: Re: [PATCH v3] glossary: add definition for overlay Date: Fri, 22 Mar 2019 13:54:51 +0900 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Philip Oakley's message of "Thu, 21 Mar 2019 14:48:28 +0000") Philip Oakley <email@example.com> writes: >> of 'cp -R'. I thought of making the same clarification for 'rsync >> --delete' as well, however I think with it being explicitly specified >> for 'cp -R', readers should be able to deduce that we are talking >> about the destination directory there as well. > As a historically Windows user, we should ensure that the meaning is > clear to all without the otherwise helpful *nix command examples. I do not know about "cp -R", but surely "rsync" is used by Windows users as well as users of Unix based systems, isn't it? >> + Only update and add files to the working directory, but don't >> + delete them, similar to how 'cp -R' would update the contents > perhaps s/them/any files/ Probably. The paths that are not deleted are certainly different set of paths from those that are updated and/or added, so it sounds like a reasonable thing to do. >> + in the destination directory. This is the default mode in a >> + <<def_checkout,checkout>> when checking out files from the >> + <<def_index,index>> or a <<def_tree-ish,tree-ish>>. In >> + contrast, no-overlay mode also deletes tracked files not > > understanding the past/future distinction is tricky here. Maybe > 'deletes previously tracked files that are no longer present in the > new source'. > > It's tricky talking about deleting things that are not there. I am afraid that "previously" may be taken too literally by readers and misunderstood as paths that had been tracked even once in the past. If you think that is worried too much because we can only delete what is _currently_ in the index, and any past before what is in the current index cannot ever affect the outcome, the same reasoning tells me that the original is clear enough without "previously", i.e. "tracked ones not present in..." are the ones that are in the index currently, but the tree that we are taking new contents from does not have them. I dunno. >> + present in the source, similar to 'rsync --delete'.
next prev parent reply other threads:[~2019-03-22 4:54 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-06 1:34 What's cooking in git.git (Mar 2019, #01; Wed, 6) Junio C Hamano 2019-03-06 1:41 ` Denton Liu 2019-03-06 23:43 ` Junio C Hamano 2019-03-06 4:43 ` Jeff King 2019-03-06 23:45 ` Junio C Hamano 2019-03-06 9:44 ` Duy Nguyen 2019-03-06 23:46 ` Junio C Hamano 2019-03-07 12:34 ` Philip Oakley 2019-03-07 12:54 ` Duy Nguyen 2019-03-09 17:27 ` Thomas Gummerer 2019-03-09 18:04 ` Elijah Newren 2019-03-10 18:27 ` Thomas Gummerer 2019-03-12 23:30 ` [PATCH v2] glossary: add definition for overlay Thomas Gummerer 2019-03-13 1:13 ` Duy Nguyen 2019-03-15 22:31 ` Thomas Gummerer 2019-03-13 1:42 ` Junio C Hamano 2019-03-15 23:10 ` Thomas Gummerer 2019-03-17 20:19 ` [PATCH v3] " Thomas Gummerer 2019-03-21 14:48 ` Philip Oakley 2019-03-22 4:54 ` Junio C Hamano [this message] 2019-03-28 21:05 ` Thomas Gummerer 2019-03-08 0:02 ` What's cooking in git.git (Mar 2019, #01; Wed, 6) Junio C Hamano 2019-03-06 12:39 ` Johannes Schindelin 2019-03-18 7:08 ` Junio C Hamano 2019-03-06 12:47 ` Johannes Schindelin 2019-03-06 23:55 ` Junio C Hamano 2019-03-06 13:26 ` Johannes Schindelin 2019-03-06 13:41 ` ps/stash-in-c, was " Johannes Schindelin 2019-03-06 23:56 ` Junio C Hamano 2019-03-06 18:10 ` Jonathan Tan 2019-03-07 0:19 ` Junio C Hamano
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
firstname.lastname@example.org list mirror (unofficial, one of many) This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 git git/ https://public-inbox.org/git \ email@example.com public-inbox-index git Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.io/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ code repositories for the project(s) associated with this inbox: https://80x24.org/mirrors/git.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git