From: Bert Wesarg <bert.wesarg@googlemail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [TopGit PATCH] pre-commit: check .topdeps for valid branches
Date: Thu, 4 Jun 2009 14:18:04 +0200 [thread overview]
Message-ID: <36ca99e90906040518h4bb92638y4d63fb5507b500a6@mail.gmail.com> (raw)
In-Reply-To: <20090604093456.GA14548@pengutronix.de>
2009/6/4 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
> Hi Bert,
>
>> diff --git a/hooks/pre-commit.sh b/hooks/pre-commit.sh
>> index 8e05a4e..1eae2e8 100644
>> --- a/hooks/pre-commit.sh
>> +++ b/hooks/pre-commit.sh
>> @@ -52,6 +52,9 @@ BEGIN { in_hunk = 0; }
>> /^[^@ +-]/ { in_hunk = 0; }
>> ' |
>> while read newly_added; do
>> + ref_exists "$newly_added" ||
>> + die "Invalid branch as dependent: $newly_added"
>> +
>> # deps can be non-tgish but we can't run recurse_deps() on them
>> ref_exists "refs/top-bases/$newly_added" ||
>> continue
>> --
>> tg: (0f8cd77..) bw/check-valid-deps (depends on: bw/check-for-dep-cycle)
> this patch doesn't apply to my branch. I'd say you didn't send out
> bw/check-for-dep-cycle (or I oversaw it).
I have forwarded it to you, but you may also want to clone my topgit tree at:
http://kgb2.thruhere.net/git/?p=bertw/topgit.git;a=summary
Now that repo.or.cz is up again, I will put this repo on this server next week.
Regards,
Bert
>
> Best regards
> Uwe
next prev parent reply other threads:[~2009-06-04 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1243592316-10820-1-git-send-email-bert.wesarg@googlemail.com>
2009-06-02 21:09 ` [TopGit PATCH] pre-commit: check .topdeps for valid branches Bert Wesarg
2009-06-04 9:34 ` Uwe Kleine-König
2009-06-04 12:18 ` Bert Wesarg [this message]
2010-10-04 21:07 [TopGit PATCH] hooks/pre-commit: check for cycles in dependencies Bert Wesarg
2010-10-04 21:18 ` [TopGit PATCH] pre-commit: check .topdeps for valid branches 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
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=36ca99e90906040518h4bb92638y4d63fb5507b500a6@mail.gmail.com \
--to=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.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).