From: Jeff King <peff@peff.net>
To: Stanislav Kolotinskiy <stanislav@assembla.com>
Cc: Dave Borowitz <dborowitz@google.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-send-pack: Fix --all option when used with directory
Date: Thu, 24 Mar 2016 13:37:31 -0400 [thread overview]
Message-ID: <20160324173731.GD6341@sigill.intra.peff.net> (raw)
In-Reply-To: <56F3F267.30900@assembla.com>
On Thu, Mar 24, 2016 at 03:57:59PM +0200, Stanislav Kolotinskiy wrote:
> On 23/03/16 23:22, Jeff King wrote:
> >Not that it matters for this bug, but for my own curiosity, what do you
> >use "send-pack --all" for? I've generally assumed that nobody directly
> >calls send-pack themselves these days, but of course we have no data to
> >support that either way. So I am always interested to hear about unusual
> >use cases.
> Well, here at Assembla we're using send-pack --all for creating forks
> from repos in a quick and efficient way.
I guess a follow-up to my question is: what does "git send-pack" do that
"git push" does not? Again, this is just for my curiosity (the answer
may be "nothing, we just happened to build our scripts around
send-pack", and that is perfectly fine).
-Peff
next prev parent reply other threads:[~2016-03-24 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 16:24 [PATCH] git-send-pack: Fix --all option when used with directory Stanislav Kolotinskiy
2016-03-23 21:22 ` Jeff King
2016-03-23 21:30 ` Jeff King
2016-03-24 13:57 ` Stanislav Kolotinskiy
2016-03-24 17:37 ` Jeff King [this message]
2016-03-24 17:49 ` Stanislav Kolotinskiy
2016-03-24 16:11 ` Junio C Hamano
2016-03-24 17:47 ` Stanislav Kolotinskiy
2016-03-24 18:02 ` Jeff King
2016-04-01 10:42 ` Stanislav Kolotinskiy
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=20160324173731.GD6341@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dborowitz@google.com \
--cc=git@vger.kernel.org \
--cc=stanislav@assembla.com \
/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).