From: Clemens Buchacher <drizzd@aon.at>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2010, #04; Wed, 12)
Date: Sat, 15 May 2010 11:04:58 +0200 [thread overview]
Message-ID: <20100515090458.GA7712@localhost> (raw)
In-Reply-To: <7vzl057dt9.fsf@alter.siamese.dyndns.org>
Hi Junio,
On Wed, May 12, 2010 at 12:57:06AM -0700, Junio C Hamano wrote:
> [Cooking]
> * cb/assume-unchanged-fix (2010-05-01) 2 commits
> - Documentation: git-add does not update files marked "assume unchanged"
> - do not overwrite files marked "assume unchanged"
Without this patch, git silently overwrites work tree files, while the
documentation claims it's safe. I was therefore expecting this to go to
master, possibly even maint.
Is there something controversial about these patches that I'm not aware of?
If so, we should at least fix the documentation in the meantime.
Cheers,
Clemens
prev parent reply other threads:[~2010-05-15 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 7:57 What's cooking in git.git (May 2010, #04; Wed, 12) Junio C Hamano
2010-05-15 9:04 ` Clemens Buchacher [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100515090458.GA7712@localhost \
--to=drizzd@aon.at \
--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.
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 NNTP newsgroup(s).