public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Neal Kreitzinger <nkreitzinger@gmail•com>
To: git@vger•kernel.org
Cc: "Levend Sayar" <levendsayar@gmail•com>,
	git@vger•kernel.org, "Neal Kreitzinger" <neal@rsss•com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail•com>
Subject: Re: clone --bare vs push
Date: Mon, 03 Jan 2011 23:29:27 -0600	[thread overview]
Message-ID: <4D22B037.9010408@gmail.com> (raw)
In-Reply-To: <20110104045839.GA8225@burratino>

On 1/3/2011 10:58 PM, Jonathan Nieder wrote:
> Neal Kreitzinger wrote:
>
>> you can also use the file:// url format to create a complete copy and not
>> use hardlinks.  see git-clone manpage.
>>
>> e.g. git clone --bare file:///fullpathto/X y.git
>
> Thanks, that's useful; cc-ing Levend.
>
> [Side note: I wrote in the past:
>
> | In traditional newsgroups it seems to be most common to just reply to
> | the author by mail or follow-up to the group, so I wouldn't feel too
> | bad.
>
> but probably that was unclear of me.  The convention on _this_ list[1] is
> to reply to all participants in a thread, so new participants do not
> need to subscribe if they don't want to.  Thunderbird (e.g.) seems to
> be good at doing that for what it's worth.]
>
> [1] at least as I perceive it; please feel free to correct me if I
> have misunderstood

This is a "reply all" from thunderbird.  This looks like it is doing the 
cc correctly...

v/r,
Neal

      reply	other threads:[~2011-01-04  5:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=+cRqD_CDFyaYj8uWOxUA1+5Dgr_pv1guaaT40@mail.gmail.com>
2011-01-03 18:24 ` clone --bare vs push Levend Sayar
2011-01-03 18:41   ` Ævar Arnfjörð Bjarmason
2011-01-04  4:40   ` Neal Kreitzinger
2011-01-04  4:58     ` Jonathan Nieder
2011-01-04  5:29       ` Neal Kreitzinger [this message]

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=4D22B037.9010408@gmail.com \
    --to=nkreitzinger@gmail$(echo .)com \
    --cc=avarab@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=levendsayar@gmail$(echo .)com \
    --cc=neal@rsss$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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