From: martin f krafft <madduck@madduck.net>
To: git discussion list <git@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Sam Vilain <sam@vilain.net>
Subject: Re: git-push [--all] and tags
Date: Sun, 7 Oct 2007 10:36:36 +0100 [thread overview]
Message-ID: <20071007093636.GA3568@lapse.madduck.net> (raw)
In-Reply-To: <alpine.LFD.0.999.0710061814310.23684@woody.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
also sprach Linus Torvalds <torvalds@linux-foundation.org> [2007.10.07.0226 +0100]:
> Well, I agrewe with Martin, and I think you missed his point.
(he did)
> Hmm? I do agree with "git push" as it now stands has a lot of warts,
> although I don't really agree with the people who want to change the
> default behavior.
So am I right if I say that all the logic should really be happening
in send-pack and that push is really just an interface when it comes
to selecting the refs to push, so it should basically feed through
the options and refs, meaning that send-pack should get --tags and
--shared as well?
Or should push enumerate all refs needed and pass them directly to
send-pack, effectively making send-pack's --all option obsolete?
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
"time flies like an arrow. fruit flies like a banana."
-- groucho marx
(panda eats shoots and leaves)
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-07 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 16:05 git-push [--all] and tags martin f krafft
2007-10-07 1:02 ` Sam Vilain
2007-10-07 1:26 ` Linus Torvalds
2007-10-07 9:36 ` martin f krafft [this message]
2007-10-07 16:39 ` Linus Torvalds
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=20071007093636.GA3568@lapse.madduck.net \
--to=madduck@madduck.net \
--cc=git@vger.kernel.org \
--cc=sam@vilain.net \
--cc=torvalds@linux-foundation.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).