All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Carnecky <tomas.carnecky@gmail.com>
To: Robert Clausecker <fuzxxl@gmail.com>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	git@vger.kernel.org
Subject: Re: Feature request: Allow extracting revisions into directories
Date: Mon, 04 Feb 2013 12:47:45 +0000	[thread overview]
Message-ID: <1359982065-ner-9588@calvin> (raw)
In-Reply-To: <1359980045.24730.32.camel@t520>

On Mon, 04 Feb 2013 13:14:05 +0100, Robert Clausecker <fuzxxl@gmail.com> wrote:
> Of course that is a possibility but it does not not feel right and is
> not intuitive. Adding this feature won't cause feature creep but would
> rather add an operation that makes sense in some scenarios and reduces
> the dependencies on other commands that might not be available on other
> platforms (If you care about that).

I'd really like to see your reply to Sitaram's email regarding the many
options that tar has. Sure, just teaching git-archive the equivalent of `|tar
-x' probably isn't feature creep. But why stop there and not add some of the
other options as well? After all, some might be equally useful in a different
situation. So where do you stop? When you've completely merged tar into git?

> Also, this functionality is in full accordance with the Unix principle
> as it is a basic operation ("put tree into files") and not something
> super special.

That's what `git checkout` is for. And I would even argue that it's the better
choice in your situation because it would delete files from /var/www/foo which
you have deleted in your repo. git archive|tar wouldn't do that.

  reply	other threads:[~2013-02-04 12:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-03 14:18 Feature request: Allow extracting revisions into directories Robert Clausecker
2013-02-03 16:25 ` Sitaram Chamarty
2013-02-03 18:11   ` Robert Clausecker
2013-02-04  0:42     ` Sitaram Chamarty
2013-02-05 15:11       ` Phil Hord
2013-02-09 15:58         ` Robert Clausecker
2013-02-09 23:00           ` Junio C Hamano
2013-02-10  3:45             ` Junio C Hamano
2013-02-10  3:57               ` Robert Clausecker
2013-02-10  4:06                 ` Jonathan Nieder
2013-02-10  4:10                   ` Robert Clausecker
2013-02-10  4:19                     ` Jonathan Nieder
2013-02-03 23:26 ` Konstantin Khomoutov
2013-02-04 11:18 ` Michael J Gruber
2013-02-04 12:14   ` Robert Clausecker
2013-02-04 12:47     ` Tomas Carnecky [this message]
2013-02-04 16:52       ` Junio C Hamano
2013-02-05  8:55         ` Sitaram Chamarty
2013-02-04 12:58     ` Andrew Ardill
2013-02-04 16:55       ` Junio C Hamano
2013-02-04 18:21     ` Andreas Schwab
2013-02-10 12:16     ` Thomas Koch

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=1359982065-ner-9588@calvin \
    --to=tomas.carnecky@gmail.com \
    --cc=fuzxxl@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.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.