[PATCH] doc/bundle: Use the more conventional suffix '.bundle'

[PATCH] doc/bundle: Use the more conventional suffix '.bundle'

[Santi Béjar]

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.

Signed-off-by: Santi Béjar <santi@agolina.net>
---
 Documentation/git-bundle.txt |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt
index ea0f6a0..57590b1 100644
--- a/Documentation/git-bundle.txt
+++ b/Documentation/git-bundle.txt
@@ -107,17 +107,17 @@ incremental bundle,
 
 ----------------
 machineA$ cd R1
-machineA$ git bundle create file.bdl master
+machineA$ git bundle create file.bundle master
 machineA$ git tag -f lastR2bundle master
 ----------------
 
-Then you sneakernet file.bdl to the target machine B. Because you don't
+Then you sneakernet file.bundle to the target machine B. Because you don't
 have to have any object to extract objects from such a bundle, not only
 you can fetch/pull from a bundle, you can clone from it as if it was a
 remote repository.
 
 ----------------
-machineB$ git clone /home/me/tmp/file.bdl R2
+machineB$ git clone /home/me/tmp/file.bundle R2
 ----------------
 
 This will define a remote called "origin" in the resulting repository that
@@ -126,12 +126,12 @@ have an entry like this:
 
 ------------------------
 [remote "origin"]
-    url = /home/me/tmp/file.bdl
+    url = /home/me/tmp/file.bundle
     fetch = refs/heads/*:refs/remotes/origin/*
 ------------------------
 
 You can fetch/pull to update the resulting mine.git repository after
-replacing the bundle you store at /home/me/tmp/file.bdl with incremental
+replacing the bundle you store at /home/me/tmp/file.bundle with incremental
 updates from here on.
 
 After working more in the original repository, you can create an
@@ -139,11 +139,11 @@ incremental bundle to update the other:
 
 ----------------
 machineA$ cd R1
-machineA$ git bundle create file.bdl lastR2bundle..master
+machineA$ git bundle create file.bundle lastR2bundle..master
 machineA$ git tag -f lastR2bundle master
 ----------------
 
-and sneakernet it to the other machine to replace /home/me/tmp/file.bdl,
+and sneakernet it to the other machine to replace /home/me/tmp/file.bundle,
 and pull from it.
 
 ----------------
-- 
1.6.1.258.g7ff14

Re: [PATCH] doc/bundle: Use the more conventional suffix '.bundle'

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

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.

General Query:
Is the bundle format stable enough to register a MIME-type (and associated 
extensions)?
-- 
Boyd Stephen Smith Jr.                   ,= ,-_-. =.
bss@iguanasuicide.net                   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy         `-'(. .)`-'
http://iguanasuicide.net/                    \_/


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [PATCH] doc/bundle: Use the more conventional suffix '.bundle'

[Santi Béjar]

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/                    \_/
>
>

Re: [PATCH] doc/bundle: Use the more conventional suffix '.bundle'

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]

On Sunday 08 February 2009 03:41:04 Santi Béjar wrote:
> 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.

Why not?  It seems preferable to use .bundle since it is more easily 
recognized, but .bdl is nice for system that are limited to a 3 byte 
extensions.  Existing MIME types have multiple extensions.  It is unlikely Git 
is run on a system that only allows 3 bytes extensions though, most of the 
ones that I'm aware of don't like 38 byte filenames.  

I'm warming to this patch
-- 
Boyd Stephen Smith Jr.                   ,= ,-_-. =.
bss@iguanasuicide.net                   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy         `-'(. .)`-'
http://iguanasuicide.net/                    \_/


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [PATCH] doc/bundle: Use the more conventional suffix '.bundle'

[Johannes Schindelin]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 684 bytes --]

Hi,

On Sat, 7 Feb 2009, Boyd Stephen Smith Jr. wrote:

> 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.

Why should that pose any problems?  We are living in the 21st century, and 
even that crappy FS called FAT knows how to handle "extensions" longer 
than 3 characters.

Rather than making it confusing for everybody, we could drag some DOS 
types (kicking and screaming, probably) into their future.

Ciao,
Dscho