git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santi Béjar" <santi@agolina.net>
To: "Boyd Stephen Smith Jr." <bss@iguanasuicide.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] doc/bundle: Use the more conventional suffix '.bundle'
Date: Sun, 8 Feb 2009 10:41:04 +0100	[thread overview]
Message-ID: <adf1fd3d0902080141s11b53127ufa83918c00b4579b@mail.gmail.com> (raw)
In-Reply-To: <200902072302.36991.bss@iguanasuicide.net>

2009/2/8 Boyd Stephen Smith Jr. <bss@iguanasuicide.net>:
> On Saturday 07 February 2009 16:21:49 Santi Béjar wrote:
>> Although it does not matter in general it is handled different by
>> "git clone", as it removes it to make the "humanish" name of the
>> new repository.
>
> I'm mixed on this, particularly with the increasing numbers of MySysGit users
> we attract.  Perhaps it would be better to teach clone to remove .bdl as well.

I don't have an opinion as I don't know exactly the situation for
MSysGit users, but I don't think it is a good idea to have two
suffixes.

>
> General Query:
> Is the bundle format stable enough to register a MIME-type (and associated
> extensions)?

At least the signature yes:

static const char bundle_signature[] = "# v2 git bundle\n";


> --
> Boyd Stephen Smith Jr.                   ,= ,-_-. =.
> bss@iguanasuicide.net                   ((_/)o o(\_))
> ICQ: 514984 YM/AIM: DaTwinkDaddy         `-'(. .)`-'
> http://iguanasuicide.net/                    \_/
>
>

  reply	other threads:[~2009-02-08  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07 22:21 [PATCH] doc/bundle: Use the more conventional suffix '.bundle' Santi Béjar
2009-02-08  5:02 ` Boyd Stephen Smith Jr.
2009-02-08  9:41   ` Santi Béjar [this message]
2009-02-08 10:04     ` Boyd Stephen Smith Jr.
2009-02-08 10:41   ` 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=adf1fd3d0902080141s11b53127ufa83918c00b4579b@mail.gmail.com \
    --to=santi@agolina.net \
    --cc=bss@iguanasuicide.net \
    --cc=git@vger.kernel.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).