From: Duy Nguyen <pclouds@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
git-for-windows <git-for-windows@googlegroups.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.9.3
Date: Mon, 22 Aug 2016 21:04:53 +0700 [thread overview]
Message-ID: <CACsJy8A3tkMY-iLPCDj9sqB4HpAK_cxsUu5Z7fsGcCQEORyxUg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1608181022250.4924@virtualbox>
On Thu, Aug 18, 2016 at 3:37 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi Junio,
>
> On Wed, 17 Aug 2016, Junio C Hamano wrote:
>
>> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>>
>> >> 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.
>> >
>> > Right. I would like to ask for a `--smudge` synonym nevertheless, just
>> > because I already use this. On the other hand, it is early enough to tell
>> > everybody who knows about this feature to change their invocation (anybody
>> > who would know about `--smudge` would be in that 1% of users that have
>> > read the release notes, so most likely would read the next release notes,
>> > too).
>>
>> It is OK if it were your private edition, but you end up hurting
>> your users if you need to redo the feature differently.
>
> Unfortunately, this is the situation of Git for Windows from its
> beginning: there has not been a single time that Git for Windows could
> live with unpatched upstream Git's source code.
>
> Business as usual, though.
Bug fixes is one thing, features is completely different. Should we
just acknowledge git-for-windows as a long-living fork and rename it
to something else? Because if somebody comes here with a "git" problem
on Windows, I would look at git.git source code, not gfw. I'd rather
recognize it a special fork (by name) right away and ignore. You could
have the same policy distros have: all bugs go to distros (i.e. gfw),
some bugs may be forwarded upstream (git.git).
--
Duy
next prev parent reply other threads:[~2016-08-22 14:05 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
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 ` Duy Nguyen [this message]
2016-08-23 13:54 ` [git-for-windows] " 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=CACsJy8A3tkMY-iLPCDj9sqB4HpAK_cxsUu5Z7fsGcCQEORyxUg@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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
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).