From: Duy Nguyen <pclouds@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Phillip Wood <phillip.wood@dunelm.org.uk>,
Derrick Stolee <dstolee@microsoft.com>, Eric Wong <e@80x24.org>
Subject: Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)
Date: Wed, 17 Apr 2019 16:33:41 +0700 [thread overview]
Message-ID: <CACsJy8B1nEKpNy8g-Ya7pgfdZwqdm8voZ0UGvMhArOjM2jPPjA@mail.gmail.com> (raw)
In-Reply-To: <87d0lmatr1.fsf@evledraar.gmail.com>
On Tue, Apr 16, 2019 at 9:51 PM Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> > * nd/precious (2019-04-09) 1 commit
> > - Introduce "precious" file concept
> >
> > "git clean" learned to pay attention to the 'precious' attributes
> > and keep untracked paths with the attribute instead of removing
> > when the "--keep-precious" is given.
> >
> > Will merge to 'next'.
>
> Duy had a message about this in
> https://public-inbox.org/git/CACsJy8AEZ-Lz6zgEsuNukvphB9TTa9FAC1gK05fhnie2xtfc9w@mail.gmail.com/
>
> If that was just a "I don't have time to deal with Ævar's deluge of
> comments" (sorry!) I'm happy to re-roll with the nits I had if anyone
> thinks those make sense (doc & test adjustments...).
>
> But that note is terse, not sure if it means "let's drop this no matter
> what" (for reasons...), ..., Duy?
I'm tired. You clearly think this is a bad idea. If it gets merge I'll
keep hearing about it. Just drop it and be done with it now.
--
Duy
next prev parent reply other threads:[~2019-04-17 9:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 13:19 What's cooking in git.git (Apr 2019, #03; Tue, 16) Junio C Hamano
2019-04-16 14:51 ` Ævar Arnfjörð Bjarmason
2019-04-16 15:26 ` Junio C Hamano
2019-04-17 7:18 ` Ævar Arnfjörð Bjarmason
2019-04-18 0:12 ` Junio C Hamano
2019-04-17 9:33 ` Duy Nguyen [this message]
2019-04-17 9:52 ` Phillip Wood
2019-04-17 10:22 ` Ævar Arnfjörð Bjarmason
2019-04-16 15:27 ` Ben Peart
2019-04-17 2:37 ` Junio C Hamano
2019-04-16 16:25 ` Stalled ds/ branches (was What's cooking in git.git (Apr 2019, #03; Tue, 16)) Derrick Stolee
2019-04-16 17:32 ` jt/clone-server-option " Jonathan Tan
2019-04-17 2:39 ` Junio C Hamano
2019-04-17 16:18 ` Jonathan Tan
2019-04-18 1:51 ` Junio C Hamano
2019-04-17 2:37 ` What's cooking in git.git (Apr 2019, #03; Tue, 16) Taylor Blau
2019-04-17 5:38 ` Junio C Hamano
2019-04-17 5:42 ` Taylor Blau
2019-04-17 6:14 ` Junio C Hamano
2019-04-18 6:54 ` Taylor Blau
2019-04-17 12:50 ` jc/format-patch-error-check, was " Johannes Schindelin
2019-04-18 0:48 ` Junio C Hamano
2019-04-17 12:52 ` ab/test-lib-pass-trace2-env, " Johannes Schindelin
2019-04-18 0:19 ` Denton Liu
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=CACsJy8B1nEKpNy8g-Ya7pgfdZwqdm8voZ0UGvMhArOjM2jPPjA@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=avarab@gmail.com \
--cc=dstolee@microsoft.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).