All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] fmt-merge-msg: use branch.$name.description
Date: Fri, 07 Oct 2011 11:45:09 +0200	[thread overview]
Message-ID: <4E8ECA25.205@drmicha.warpmail.net> (raw)
In-Reply-To: <20111007091636.GA22822@elie.hsd1.il.comcast.net>

Jonathan Nieder venit, vidit, dixit 07.10.2011 11:16:
> Michael J Gruber wrote:
> 
>> config based is so non-distributed, local in nature.
> 
> I don't follow.  Wouldn't a protocol change be enough to fix that, by
> sharing branch descriptions analagously to how refs themselves are
> shared?

I'd be surprised if we changed the protocol just to be able to share
some descriptions, when we have everything we need for sharing refs.
Also note that config is non-versioned etc.

But my main point here is that we should discuss the pros and cons of
each approach in context (the context of the original thread), and I
haven't heard many pros and cons for either.

Michael

  reply	other threads:[~2011-10-07  9:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07  6:57 [PATCH] fmt-merge-msg: use branch.$name.description Junio C Hamano
2011-10-07  8:51 ` Michael J Gruber
2011-10-07  9:16   ` Jonathan Nieder
2011-10-07  9:45     ` Michael J Gruber [this message]
2011-10-07 10:06       ` Jonathan Nieder
2011-10-07 12:14         ` Michael J Gruber
2011-10-07 19:50           ` Jonathan Nieder
2011-10-07 19:59             ` Junio C Hamano
2011-10-07 20:40               ` Michael J Gruber
2011-10-07 20:12           ` Jonathan Nieder
2011-10-07 20:59           ` Junio C Hamano
2011-10-08  0:01             ` Jakub Narebski

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=4E8ECA25.205@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.