git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: franky <yinping@kooxoo.com>
Cc: 'Lars Hjemli' <hjemli@gmail.com>, git@vger.kernel.org
Subject: RE: Is there any plan to support partial checkout or submoudule improvement?
Date: Tue, 16 Oct 2007 12:02:38 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710161158350.25221@racer.site> (raw)
In-Reply-To: <20071016082720.E5EDA7E6F@mail.kooxoo.com>

Hi,

[please do not top post.  Only keep the parts of the original message that 
you are responding to, and put your answers just below.  It is a matter of 
simple economy: it takes you just a couple of minutes, but spares those 
"millions" of readers the minutes to understand what you're talking about.  
In addition, it is a matter of politeness.]

On Tue, 16 Oct 2007, franky wrote:

> I want a single "git-pull" to deploy a new version and a
> single "git-reset" to back to versions before [on partial checkouts]

You are talking as if your partial checkout was a project in its own 
right.  Then make it so.  Do not use a partial checkout, but make that a 
submodule.

One reason _not_ to support partial checkouts is exactly to avoid people 
falling into that mousetrap of thinking that they can sensibly merge 
_parts_ of the HEAD.

Ciao,
Dscho

  parent reply	other threads:[~2007-10-16 11:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16  3:20 Is there any plan to support partial checkout or submoudule improvement? franky
2007-10-16  8:08 ` Lars Hjemli
2007-10-16  8:27   ` franky
2007-10-16  8:42     ` Lars Hjemli
2007-10-16  9:56       ` franky
2007-10-16 10:50         ` Lars Hjemli
2007-10-16 11:45           ` franky
2007-10-16 11:02     ` Johannes Schindelin [this message]
2007-10-16 11:53       ` franky
2007-10-16 21:33         ` Jan Hudec
2007-10-17  2:54           ` Is there any plan to support partial checkout or submouduleimprovement? franky

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=Pine.LNX.4.64.0710161158350.25221@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=hjemli@gmail.com \
    --cc=yinping@kooxoo.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).