From: Sverre Rabbelier <srabbelier@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Pieter de Bie <pdebie@ai.rug.nl>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2009, #07; Wed, 28)
Date: Thu, 29 Jan 2009 13:20:20 +0100 [thread overview]
Message-ID: <bd6139dc0901290420x1216a399w656e4d1622178a06@mail.gmail.com> (raw)
In-Reply-To: <20090129115026.GB10792@coredump.intra.peff.net>
On Thu, Jan 29, 2009 at 12:50, Jeff King <peff@peff.net> wrote:
> I think that would be reasonable.
Yay :).
> It wouldn't help the case of "somebody
> else pushed some content that you want to pull", but like you said, I
> think the primary workflow is that you immediately push after cloning
> the empty repo.
Also, the only way to support the "somebody else pushed already"
workflow would be to assume the user wants to name the branch
'master', which might not be the case at all.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-01-29 12:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 2:06 What's cooking in git.git (Jan 2009, #07; Wed, 28) Junio C Hamano
2009-01-29 3:38 ` Jeff King
2009-01-29 3:51 ` Jeff King
2009-01-29 4:02 ` Jeff King
2009-01-29 4:22 ` Junio C Hamano
2009-01-29 11:27 ` Sverre Rabbelier
2009-01-29 11:37 ` Jeff King
2009-01-29 11:40 ` Pieter de Bie
2009-01-29 11:45 ` Sverre Rabbelier
2009-01-29 11:50 ` Jeff King
2009-01-29 12:20 ` Sverre Rabbelier [this message]
2009-01-30 4:51 ` Jeff King
2009-01-30 13:18 ` Johannes Schindelin
2009-01-30 16:26 ` Jeff King
2009-02-01 1:31 ` Junio C Hamano
2009-02-12 6:42 ` Junio C Hamano
2009-02-12 10:51 ` Sverre Rabbelier
2009-02-12 11:04 ` Johannes Schindelin
2009-02-12 21:04 ` Junio C Hamano
2009-02-12 21:51 ` Johannes Schindelin
2009-02-12 12:32 ` Jeff King
2009-01-29 11:48 ` Jeff King
2009-01-29 12:04 ` Nico -telmich- Schottelius
2009-01-30 4:59 ` Jeff King
2009-01-29 8:14 ` Charles Bailey
2009-01-29 8:26 ` Junio C Hamano
2009-01-29 9:16 ` Charles Bailey
2009-01-30 16:32 ` Charles Bailey
2009-02-01 17:45 ` Kirill Smelkov
2009-02-01 21:34 ` 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=bd6139dc0901290420x1216a399w656e4d1622178a06@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pdebie@ai.rug.nl \
--cc=peff@peff.net \
/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).