git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git-for-windows@googlegroups.com, git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git for Windows 2.9.3
Date: Sat, 13 Aug 2016 08:50:50 -0700	[thread overview]
Message-ID: <xmqqshu8u0px.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1608131214070.4924@virtualbox> (Johannes Schindelin's message of "Sat, 13 Aug 2016 12:14:15 +0200 (CEST)")

Johannes Schindelin <johannes.schindelin@gmx.de> writes:

> New Features
>
>   • Comes with Git 2.9.3.

For future reference, what time (in UTC) of the day is convenient
for you to see an upstream tarball?

>   • Sports a new --smudge option for git cat-file that lets it pass
>     blob contents through smudge filters configured for the specified
>     path.

Perhaps we want to upstream this, together with a new "--clean"
option for git hash-object?

And after writing all of the above, I noticed that hash-object by
default uses the clean machinery and that can be turned off by
giving the "--no-filters" option.  The reason why the option is not
called "--no-clean" is because it is not just about the clean filter
but is about using the entirety of convert_to_git() filter chain.

We probably should teach "hash-objects" to take "--filters" for
consistency.

And then your "git cat-file" patch can be upstreamed with the option
renamed to (or with an additional synonym) "--filters", which would
make things consistent.

Thanks.


  reply	other threads:[~2016-08-13 15:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-13 10:14 [ANNOUNCE] Git for Windows 2.9.3 Johannes Schindelin
2016-08-13 15:50 ` Junio C Hamano [this message]
2016-08-17 13:54   ` Johannes Schindelin
2016-08-17 15:29     ` Junio C Hamano
2016-08-18  8:37       ` Johannes Schindelin
2016-08-22 14:04         ` [git-for-windows] " Duy Nguyen
2016-08-23 13:54           ` Johannes Schindelin
2016-08-23 14:41             ` Michael J Gruber
2016-08-23 15:37               ` Johannes Schindelin
2016-08-23 16:05                 ` Johannes Schindelin
2016-08-23 19:25                   ` Junio C Hamano
2016-08-23 21:42                     ` Junio C Hamano
2016-08-24  1:04                       ` Dakota Hawkins
2016-08-24 15:41                         ` Git for Windows documentation, was " Johannes Schindelin
2016-08-24 16:06                           ` Dakota Hawkins
2016-08-24 23:28                             ` Philip Oakley
2016-08-25 11:42                             ` Johannes Schindelin
2016-08-24 15:39                     ` Johannes Schindelin
2016-08-24  5:09                   ` Junio C Hamano
2016-08-24 15:48                     ` core.autocrlf, was " Johannes Schindelin
2016-08-24 16:45                       ` Junio C Hamano
2016-08-25 11:54                         ` Johannes Schindelin
2016-08-25 12:43                           ` Torsten Bögershausen
2016-08-25 13:50                             ` Johannes Schindelin

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=xmqqshu8u0px.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git-for-windows@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    /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).