From: "Santi Béjar" <santi@agolina.net>
To: Mike Hommey <mh@glandium.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] contrib: add 'git bpush' to push to bundles
Date: Thu, 29 Jan 2009 17:05:53 +0100 [thread overview]
Message-ID: <adf1fd3d0901290805s64161899u72905a31dfec2fc6@mail.gmail.com> (raw)
In-Reply-To: <20090120064732.GA14580@glandium.org>
2009/1/20 Mike Hommey <mh@glandium.org>:
> On Tue, Jan 20, 2009 at 12:46:31AM +0100, Santi Béjar wrote:
>> 'git bpush' updates the branches in a bundle, while adding the objects
>> necessary to complete the given branches. Basically, it is a 'git
>> push' for bundles.
>
> I think it'd be better to improve git-push to support that, instead of
> adding yet another git command.
Yes, I also think it'd be better if git-push supports it, but this is
not a trivial task, and my script works now. So I think it makes sense
to add it to the *contrib* directory.
Santi
prev parent reply other threads:[~2009-01-29 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 23:46 [PATCH] contrib: add 'git bpush' to push to bundles Santi Béjar
2009-01-20 6:47 ` Mike Hommey
2009-01-29 16:05 ` Santi Béjar [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=adf1fd3d0901290805s64161899u72905a31dfec2fc6@mail.gmail.com \
--to=santi@agolina.net \
--cc=git@vger.kernel.org \
--cc=mh@glandium.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).