git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sean <seanlkml@sympatico.ca>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Carl Worth <cworth@cworth.org>,
	Barry Fishman <barry_fishman@acm.org>,
	git@vger.kernel.org
Subject: Re: Problems setting up bare repository (git 1.5.3.3)
Date: Tue, 02 Oct 2007 12:09:10 -0700	[thread overview]
Message-ID: <7vfy0tl4fd.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <BAYC1-PASMTP05AB6AE16E90C15710819EAEAE0@CEZ.ICE> (seanlkml@sympatico.ca's message of "Tue, 2 Oct 2007 14:55:56 -0400")

Sean <seanlkml@sympatico.ca> writes:

> On Tue, 02 Oct 2007 11:23:39 -0700
> Junio C Hamano <gitster@pobox.com> wrote:
>
>> If your push were "next~27^2:frotz", it becomes even less clear.
>> It may be that I am pushing out the tip of a topic branch I
>> usually do not push out, so it would be easier for some specific
>> person to build on top of.  Or maybe I am marking that place as
>> a lightweight tag.  They are equally likely.
>
> But you could pick a reasonable default in assuming that a new
> branch is desired with the above example.  If someone wants to
> push a tag, they can create the tag locally, and then push it.

I think you are on the same page.

We can pick _a_ default, and tell people that if they want a
non-default behaviour, they have to be explicit.  That goes
without saying.

The discussion between Johannes and I was about picking what
default is _reasonable_; Johannes made it sound like branches
are norm and tags are oddball.  I was merely pointing out that
it won't be so cut-and-dried.

  reply	other threads:[~2007-10-02 19:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01 21:46 Problems setting up bare repository (git 1.5.3.3) Barry Fishman
2007-10-01 22:32 ` Junio C Hamano
2007-10-01 23:06   ` Carl Worth
2007-10-01 23:17     ` J. Bruce Fields
2007-10-01 23:24     ` Junio C Hamano
2007-10-01 23:47       ` Carl Worth
2007-10-01 23:35     ` Shawn O. Pearce
2007-10-02  9:46     ` Johannes Schindelin
2007-10-02 13:54       ` Barry Fishman
2007-10-02 17:40         ` Johannes Schindelin
2007-10-02 19:54           ` Barry Fishman
2007-10-02 15:39       ` Carl Worth
2007-10-02 17:45         ` Johannes Schindelin
2007-10-02 18:23           ` Junio C Hamano
2007-10-02 18:55             ` Sean
2007-10-02 19:09               ` Junio C Hamano [this message]
2007-10-02 21:02                 ` Johannes Schindelin
2007-10-02 20:59               ` Johannes Schindelin

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=7vfy0tl4fd.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=barry_fishman@acm.org \
    --cc=cworth@cworth.org \
    --cc=git@vger.kernel.org \
    --cc=seanlkml@sympatico.ca \
    /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).