From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: Petr Baudis <pasky@suse.cz>,
git@vger.kernel.org, martin f krafft <madduck@debian.org>
Subject: Re: [TopGit PATCH] pre-commit: check .top* files in the to-be-commited tree
Date: Thu, 4 Jun 2009 07:27:16 +0200 [thread overview]
Message-ID: <20090604052716.GA24414@pengutronix.de> (raw)
In-Reply-To: <1243975238-4807-1-git-send-email-bert.wesarg@googlemail.com>
Hi Bert,
On Tue, Jun 02, 2009 at 10:40:38PM +0200, Bert Wesarg wrote:
> We currently check fo these files only in the working tree. But we should check
> what would be commited. We use write-tree to be able to utilize ls-tree and
> check the result.
<nitpick> I prefer not speaking about "us" in the commit log. Better
use passive voice. </nitpick> So what about:
The pre-commit hook used to check that the working copy has the .top*
files. Instead of that assert that the tree that is about to be
commited has these files.
> +# I suspect this can't fail, but who knows
> +tree=$(git write-tree) ||
> + die "Can't write tree"
Actually you don't need to write the tree. You can use:
git cat-file -t :0:.topdeps
-> blob
git cat-file blob :0:.topdeps | grep .
Up to now I only shortly looked at your patches, but they seem to be OK.
I hope I get around to push the changes later today.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2009-06-04 5:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 20:40 [TopGit PATCH] pre-commit: check .top* files in the to-be-commited tree Bert Wesarg
2009-06-04 5:27 ` Uwe Kleine-König [this message]
2009-06-04 21:29 ` Bert Wesarg
-- strict thread matches above, loose matches on Subject: below --
2010-10-04 18:54 Bert Wesarg
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=20090604052716.GA24414@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=madduck@debian.org \
--cc=pasky@suse.cz \
/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).