From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Marc Weber <marco-oweber@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] topgit tg push feature
Date: Mon, 11 May 2009 21:55:32 +0200 [thread overview]
Message-ID: <20090511195532.GA28340@pengutronix.de> (raw)
In-Reply-To: <20090511032813.GA15540@gmx.de>
Hi Marc,
just some random nitpicks on top of your patch:
diff --git a/tg-push.sh b/tg-push.sh
index 0fa7854..8897a18 100644
--- a/tg-push.sh
+++ b/tg-push.sh
@@ -8,7 +8,7 @@ remotes=
recurse_deps=true
tgish_deps_only=false
-dry_run=false
+dry_run=
while [ -n "$1" ]; do
arg="$1"; shift
@@ -16,11 +16,11 @@ while [ -n "$1" ]; do
--no-deps)
recurse_deps=false;;
--dry-run)
- dry_run=true;;
+ dry_run="--dry-run";;
--tgish-only)
tgish_deps_only=true;;
-h|--help)
- echo "Usage: tg push [(--dry-run | --no-deps | --tgish-only)] [-r "remote remote2"]* branch*"
+ echo "Usage: tg push [--dry-run] [--no-deps] [--tgish-only] [-r "remote remote2"]* branch*"
exit 1;;
-r)
remotes="$remotes $1"
@@ -44,12 +44,12 @@ if [ -z "$branches" ]; then
fi
for name in $branches; do
- ref_exists "$name" || die "detached HEAD? Can't push that"
+ ref_exists "$name" || die "detached HEAD? Can't push $name"
done
push_branch(){
# if so desired omit non tgish deps
- $tgish_deps_only && [ -z "$_dep_is_tgish" ] && return 0
+ $tgish_deps_only && [ -z "$_dep_is_tgish" ] && return 0
echo "$_dep"
local base="top-bases/$_dep"
@@ -73,10 +73,6 @@ for remote in $remotes; do
push_branch "$name"
)"
echo "pushing:"; echo $list
- if $dry_run; then
- echo git push $remote $list
- else
- git push $remote $list
- fi
+ git push $dry_run "$remote" $list
done
done
--
1.6.2.4
It's untested, but I think it should be enough if it is eyeballed by
someone else.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2009-05-11 19:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 16:13 [PATCH] topgit tg push feature Marc Weber
2009-04-25 16:34 ` Marc Weber
2009-05-05 9:34 ` Marc Weber
2009-05-07 4:59 ` Marc Weber
2009-05-07 5:45 ` Bert Wesarg
2009-05-07 8:43 ` Uwe Kleine-König
2009-05-07 9:50 ` Bert Wesarg
2009-05-09 10:36 ` martin f krafft
2009-05-09 19:09 ` Marc Weber
2009-05-11 3:28 ` Marc Weber
2009-05-11 7:25 ` martin f krafft
2009-05-11 7:47 ` martin f krafft
2009-05-11 19:55 ` Uwe Kleine-König [this message]
2009-05-11 21:06 ` Marc Weber
2009-05-11 21:39 ` martin f krafft
2009-05-12 5:13 ` Uwe Kleine-König
2009-05-12 6:22 ` Bert Wesarg
2009-05-12 7:54 ` Marc Weber
2009-05-12 8:55 ` Bert Wesarg
2009-05-12 9:02 ` Uwe Kleine-König
2009-05-13 10:04 ` [PATCH] tg-remote: don't add push specs but warn about existing ones Uwe Kleine-König
2009-05-13 11:42 ` martin f krafft
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=20090511195532.GA28340@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=git@vger.kernel.org \
--cc=marco-oweber@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.
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).