All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <cel@citi.umich.edu>
To: cel@citi.umich.edu
Cc: Pavel Roskin <proski@gnu.org>,
	Catalin Marinas <catalin.marinas@gmail.com>,
	git <git@vger.kernel.org>
Subject: Re: [PATCH] stgit: fix clone
Date: Wed, 11 Jan 2006 17:47:15 -0500	[thread overview]
Message-ID: <43C58AF3.10606@citi.umich.edu> (raw)
In-Reply-To: <43C58916.6030409@citi.umich.edu>

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

Chuck Lever wrote:
> hi pavel-
> 
> exactly where does the clone operation fail?  is it at the checkout step?
> 
> seems to me the "git clone" script should create an environment where 
> "git-rev-parse --git-dir" ought to work correctly.

oops.  i see it now.

stgit/main.py does a special stack.Series('master') just for the clone 
command.  it really shouldn't do this -- the crt_series.init() in the 
clone command ought to be fixed to do this properly.

catalin, do you agree?

[-- Attachment #2: cel.vcf --]
[-- Type: text/x-vcard, Size: 451 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Charles
org:Network Appliance, Incorporated;Open Source NFS Client Development
adr:535 West William Street, Suite 3100;;Center for Information Technology Integration;Ann Arbor;MI;48103-4943;USA
email;internet:cel@citi.umich.edu
title:Member of Technical Staff
tel;work:+1 734 763-4415
tel;fax:+1 734 763 4434
tel;home:+1 734 668-1089
x-mozilla-html:FALSE
url:http://troy.citi.umich.edu/u/cel/
version:2.1
end:vcard


  reply	other threads:[~2006-01-11 22:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 22:19 [PATCH] stgit: fix clone Pavel Roskin
2006-01-11 22:39 ` Chuck Lever
2006-01-11 22:47   ` Chuck Lever [this message]
2006-01-12 11:54     ` Catalin Marinas
2006-01-12 14:51       ` Chuck Lever
2006-01-13  5:24       ` Pavel Roskin

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=43C58AF3.10606@citi.umich.edu \
    --to=cel@citi.umich.edu \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=proski@gnu.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 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.