From: Thomas Gummerer <t.gummerer@gmail.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Philip Oakley <philipoakley@iee.org>,
Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>,
Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH v2] glossary: add definition for overlay
Date: Fri, 15 Mar 2019 22:31:25 +0000
Message-ID: <20190315223125.GG16414@hank.intra.tgummerer.com> (raw)
In-Reply-To: <CACsJy8B4gEwuyVV_T+vYdMNjs-01rxCk5G9yxbJOSkKWHGgnSg@mail.gmail.com>
On 03/13, Duy Nguyen wrote:
> On Wed, Mar 13, 2019 at 6:30 AM Thomas Gummerer <t.gummerer@gmail.com> wrote:
> >
> > Add a definition for what overlay means in the context of git, to
> > clarify the recently introduced overlay-mode in git checkout.
> >
> > Helped-by: Elijah Newren <newren@gmail.com>
> > Signed-off-by: Thomas Gummerer <t.gummerer@gmail.com>
> > ---
> >
> > v2 addresses Elijah's comments (thanks!), using the wording he
> > suggested in [*1*], which I agree is slightly better, as no-overlay
> > mode doesn't touch untracked files.
>
> It could overwrite untracked files (e.g. the file is present in the
> source, but not tracked) but never delete them. But I think it's the
> little detail that we could skip.
Right, we decided to go without that detail in the documentation for
the command line option as well [*1*]. I think the argument that an
overly precise description would make the description harder to
understand is also valid here. Though if someone can come up with a
nice phrasing for that I'd be happy to add that.
*1*: https://public-inbox.org/git/xmqqo98yiq8i.fsf@gitster-ct.c.googlers.com/
next prev parent reply other threads:[~2019-03-15 22:31 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 [this message]
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
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 \
--in-reply-to=20190315223125.GG16414@hank.intra.tgummerer.com \
--to=t.gummerer@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=newren@gmail.com \
--cc=pclouds@gmail.com \
--cc=philipoakley@iee.org \
--subject='Re: [PATCH v2] glossary: add definition for overlay' \
/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
git@vger.kernel.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 \
git@vger.kernel.org
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 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