All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Schrab <aaron@schrab.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 2/2] clone: Allow repo using gitfile as a reference
Date: Tue, 9 Apr 2013 12:31:49 -0400	[thread overview]
Message-ID: <20130409163149.GA20752@pug.qqx.org> (raw)
In-Reply-To: <20130409002456.GW30308@google.com>

At 17:24 -0700 08 Apr 2013, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> +test_expect_success 'clone using repo with gitfile as a reference' '
>> +	git clone --separate-git-dir=L A M &&
>> +	git clone --reference=M A N &&
>
>What should happen if I pass --reference=M/.git?

That isn't supported and I wouldn't expect it to work.  The --reference 
option is documented as taking the location of a repository as the 
argument and I wouldn't consider a .git file to be a repository.  I also 
can't think of a reason that it would be very useful since it should be 
simple to just refer to the directory containing the .git file.  But if 
others disagree, I could be convinced to add support for that.

I also wouldn't consider it breakage if that use would start working, so 
I don't see a point in adding a test to check that that usage fails.

>> +	echo "$base_dir/L/objects" > expected &&
>
>The usual style in tests is to include no space after >redirection
>operators.

Fixed for the next version, pending further comments.

  reply	other threads:[~2013-04-09 16:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07 23:17 [PATCH 1/2] clone: Fix error message for reference repository Aaron Schrab
2013-04-07 23:17 ` [PATCH 2/2] clone: Allow repo using gitfile as a reference Aaron Schrab
2013-04-07 23:51   ` Jonathan Nieder
2013-04-08  0:08     ` Aaron Schrab
2013-04-08 18:00       ` Junio C Hamano
2013-04-08 18:59         ` Aaron Schrab
2013-04-08 22:46           ` [PATCH v2 0/2] Using gitfile repository with clone --reference Aaron Schrab
2013-04-08 22:46             ` [PATCH 1/2] clone: Fix error message for reference repository Aaron Schrab
2013-04-09  0:18               ` Jonathan Nieder
2013-04-08 22:46             ` [PATCH 2/2] clone: Allow repo using gitfile as a reference Aaron Schrab
2013-04-09  0:24               ` Jonathan Nieder
2013-04-09 16:31                 ` Aaron Schrab [this message]
2013-04-09 16:47                   ` Junio C Hamano
2013-04-09 16:50                     ` Aaron Schrab
2013-04-09 22:21                     ` [PATCH v3 0/2] Using gitfile repository with clone --reference Aaron Schrab
2013-04-09 22:21                       ` [PATCH v3 1/2] clone: Fix error message for reference repository Aaron Schrab
2013-04-09 22:22                       ` [PATCH v3 2/2] clone: Allow repo using gitfile as a reference Aaron Schrab
2013-04-09 22:41                       ` [PATCH v3 0/2] Using gitfile repository with clone --reference Junio C Hamano
2013-04-07 23:48 ` [PATCH 1/2] clone: Fix error message for reference repository Jonathan Nieder
2013-04-08  0:06   ` Aaron Schrab
2013-04-08  1:11     ` Aaron Schrab
2013-04-08 13:58     ` Junio C Hamano
2013-04-08 14:57       ` Aaron Schrab
2013-04-08 15:30         ` Junio C Hamano
2013-04-08 16:17           ` Aaron Schrab
2013-04-08 17:57             ` Junio C Hamano
2013-04-08 18:58               ` Aaron Schrab
2013-04-08 19:10                 ` Junio C Hamano

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=20130409163149.GA20752@pug.qqx.org \
    --to=aaron@schrab.com \
    --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.