From: Petr Baudis <pasky@suse.cz>
To: Shawn Pearce <spearce@spearce.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Added --mirror-all to git-fetch.
Date: Wed, 20 Sep 2006 20:29:54 +0200 [thread overview]
Message-ID: <20060920182953.GT8259@pasky.or.cz> (raw)
In-Reply-To: <20060920173126.GG23260@spearce.org> <20060920162145.GA23260@spearce.org>
Dear diary, on Wed, Sep 20, 2006 at 06:21:45PM CEST, I got a letter
where Shawn Pearce <spearce@spearce.org> said that...
> > > combined with set of packs with staggered spans to help
> > > commit walkers Pasky talked about quite a while ago).
> >
> > Yes, this is certainly one of things I would like to implement at
> > repo.or.cz.
>
> Borrowing your line:
> Hmm, I think I've missed this, I must look that in the archive.
> :-)
I've proposed something long time ago in
<20051112135947.GC30496@pasky.or.cz>.
Dear diary, on Wed, Sep 20, 2006 at 07:31:26PM CEST, I got a letter
where Shawn Pearce <spearce@spearce.org> said that...
> Junio C Hamano <junkio@cox.net> wrote:
> > Shawn Pearce <spearce@spearce.org> writes:
> > > Originally I gave Pasky a one-liner on #git:
> > >
> > > git fetch --force origin $(git ls-remote origin \
> > > | awk '{if(!/\^{}$/){print $2":"$2}}')
> >
> > Which sounds a very sane thing to do, especially given git is
> > designed to be scripted this way.
>
> Exactly. So I'm not sure why he was against it. After all he must
> have some script that's looping over all mirrored repositories and
> invoking git fetch in them. :-)
Basically, I imagined that what I wanted would be very close or
identical to git fetch --all (or whatever you call it, just doing it
with .git/refs/remotes) which I think should certainly be supported
without funny awk pipes. ;-)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
prev parent reply other threads:[~2006-09-20 18:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 23:28 [PATCH] Added --mirror-all to git-fetch Shawn Pearce
2006-09-19 23:41 ` Petr Baudis
2006-09-20 16:06 ` Junio C Hamano
2006-09-20 16:14 ` Petr Baudis
2006-09-20 16:21 ` Shawn Pearce
2006-09-20 16:34 ` Junio C Hamano
2006-09-20 16:49 ` Shawn Pearce
2006-09-20 17:13 ` Junio C Hamano
2006-09-20 17:31 ` Shawn Pearce
2006-09-20 17:50 ` Junio C Hamano
2006-09-20 18:42 ` A Large Angry SCM
2006-09-20 21:36 ` Junio C Hamano
2006-09-20 21:42 ` Shawn Pearce
2006-09-20 18:29 ` Petr Baudis [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=20060920182953.GT8259@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.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).