git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>, Mark Levedahl <mdl123@verizon.net>
Cc: "Santi Béjar" <sbejar@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCHv2] clone: support cloning full bundles
Date: Thu, 28 Feb 2008 00:26:15 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LSU.1.00.0802280024460.22527@racer.site> (raw)
In-Reply-To: <7vpruindag.fsf@gitster.siamese.dyndns.org>

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

Hi,

On Wed, 27 Feb 2008, Junio C Hamano wrote:

> "Santi Béjar" <sbejar@gmail.com> writes:
> 
> > My preference are in order:
> >
> > 1) define an official extension + the && [ -f "$repo" ]
> > 2) the && [ -f "$repo"]
> > 3) just remove this line
> 
> Sure.  (1) sounds sane and if you make the extension ".git",
> then I do not think you need anything more ;-).  Jokes aside,
> calling it .bundle or .bndl would be sane.
> 
> Opinions?

I like .bundle, obviously (I used it in every single example I gave).

Ciao,
Dscho

P.S.: only recently, I found out how useful bundles really are.  Thanks, 
Mark, for persisting!

  reply	other threads:[~2008-02-28  0:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 10:12 [PATCHv2] clone: support cloning full bundles Santi Béjar
2008-02-25 19:30 ` Junio C Hamano
2008-02-25 20:29   ` Santi Béjar
2008-02-25 21:00     ` Junio C Hamano
2008-02-27 22:44 ` Junio C Hamano
2008-02-27 23:04   ` Santi Béjar
2008-02-27 23:16     ` Santi Béjar
2008-02-27 23:48       ` Daniel Barkalow
2008-02-28  0:19       ` Junio C Hamano
2008-02-28  0:26         ` Johannes Schindelin [this message]
2008-02-28  0:32           ` Santi Béjar
2008-02-29  4:27           ` Mark Levedahl
  -- strict thread matches above, loose matches on Subject: below --
2008-02-28  2:22 [PATCHv3] " Santi Béjar
2008-02-29 19:16 ` [PATCHv2] " Santi Béjar

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LSU.1.00.0802280024460.22527@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mdl123@verizon.net \
    --cc=sbejar@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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).