From: Jakub Narebski <jnareb@gmail.com>
To: "Kirill A. Korinskiy" <catap@catap.ru>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-push: add option --repo-all
Date: Fri, 18 Sep 2009 13:02:45 +0200 [thread overview]
Message-ID: <200909181302.49335.jnareb@gmail.com> (raw)
In-Reply-To: <877hvwzkw7.wl%catap@catap.ru>
Kirill A. Korinskiy wrote:
> At Fri, 18 Sep 2009 01:52:49 -0700 (PDT),
> Jakub Narebski <jnareb@gmail.com> wrote:
> > "Kirill A. Korinskiy" <catap@catap.ru> writes:
> > > ---
> > > Documentation/git-push.txt | 4 ++-
> > > builtin-push.c | 34 +++++++++++++++++++++-----------
> > > t/t5523-push-repo-all.sh | 46 ++++++++++++++++++++++++++++++++++++++++++++
> > > 3 files changed, 71 insertions(+), 13 deletions(-)
> > > create mode 100755 t/t5523-push-repo-all.sh
> >
> > I have created 'pushall' *alias* for that purpose, but I think that
> > such functionality would be better added to "git remote" rather than
> > to "git push".
>
> not sure, because git remote make interface for managment remotes
> repos and push make interface for pushing to remote repo. I just add a
> pushing to all repos.
>
> I thought about pushing to some remotes repos, yes, but could not come
> up with a good symantics.
Well, git-remote has "git remote update" subcommand for fetching from
a group of remote repositories, so it is not only about managing remotes.
I think "git remote push" (or something like that) would fit in
git-remote area of competence.
Besides git-remote understands groups of remote repositories for fetch
(update), which would be (I think) a good idea also for push.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2009-09-18 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 7:17 [PATCH] git-push: add option --repo-all Kirill A. Korinskiy
2009-09-18 8:52 ` Jakub Narebski
2009-09-18 10:44 ` Kirill A. Korinskiy
[not found] ` <877hvwzkw7.wl%catap@catap.ru>
2009-09-18 11:02 ` Jakub Narebski [this message]
2009-09-18 11:15 ` Paolo Bonzini
2009-09-18 16:42 ` Junio C Hamano
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=200909181302.49335.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=catap@catap.ru \
--cc=git@vger.kernel.org \
/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).