All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: <git@vger.kernel.org>, Johan Herland <johan@herland.net>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	Ramkumar Ramachandra <artagnon@gmail.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Sam Vilain <sam@vilain.net>
Subject: Re: [PATCH 2/2] fast-import: introduce "feature notes" command
Date: Wed, 2 Feb 2011 20:47:54 +0100	[thread overview]
Message-ID: <201102022047.55152.trast@student.ethz.ch> (raw)
In-Reply-To: <20110202050735.GE15285@elie>

Jonathan Nieder wrote:
> 
> Support for importing notes was added to git fast-import quite a while
> ago (v1.6.6-rc0~21^2~8, 2009-10-09), before the 'feature' facility was
> introduced (v1.7.0-rc0~95^2~4, fast-import: add feature command,
> 2009-12-04) so for compatibility with older git versions, authors
> of existing frontends should not start using the "feature notes"
> command.  Most git versions in wide use support notemodify already.
> 
> The purpose of the "feature notes" declaration is instead to
> distinguish between git and fast-import backends that do not support
> notemodify.  In git "feature notes" will be a no-op while in other
> current fast-import backends it will error out with a clear error
> message.

So in summary, don't use "feature notes" because it would fail with
old gits, but do use "feature notes" because it will fail for non-git?

Isn't that a bit backwards?  I mean, a tool author would either just
use it and say "if it doesn't read this, upgrade your git" or run

  echo feature notes | scm fast-import

to test, and use notes depending on success.  In both cases old gits
will be regarded as incompatible.  Or am I missing something?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2011-02-02 19:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02  4:58 [PATCH/RFC 0/2] fast-import: introduce "feature notes" command Jonathan Nieder
2011-02-02  5:00 ` [PATCH 1/2] Documentation/fast-import: explain how to remove a note Jonathan Nieder
2011-02-02  5:07 ` [PATCH 2/2] fast-import: introduce "feature notes" command Jonathan Nieder
2011-02-02 19:47   ` Thomas Rast [this message]
2011-02-02 19:57     ` Sverre Rabbelier
2011-02-02 20:22       ` Jonathan Nieder
2011-02-09 21:46       ` [PATCH maint-1.7.0 v2 0/2] " Jonathan Nieder
2011-02-09 22:43         ` [PATCH 1/2] fast-import: clarify documentation of "feature" command Jonathan Nieder
2011-02-09 22:43         ` [PATCH 2/2] fast-import: introduce "feature notes" command Jonathan Nieder
2011-02-09 23:06           ` Sverre Rabbelier

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=201102022047.55152.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johan@herland.net \
    --cc=jrnieder@gmail.com \
    --cc=sam@vilain.net \
    --cc=spearce@spearce.org \
    --cc=srabbelier@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.