All of lore.kernel.org
 help / color / mirror / Atom feed
From: A Large Angry SCM <gitzilla@gmail.com>
To: Anand Kumria <wildfire@progsoc.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/1]   Make git-tar-tree more flexible
Date: Sun, 30 Jul 2006 11:46:43 -0700	[thread overview]
Message-ID: <44CCFE93.7040500@gmail.com> (raw)
In-Reply-To: <20060730174847.GA32574@eve.kumria.com>

Anand Kumria wrote:
>   If you have a project which is setup like:
>      project
>      website
>   and you decide you wish to generate a tar archive of _just_ the 'project'
>   portion, git-tar-tree is not able to help. This patch adds two parameters
>   which can assist.
> 
>   The first is '--pathlimit', which forces git-tar-tree to only generate the
>   tar archive for project; as in:
>     'git tar-tree --pathlimit=project project-1.0 tag-1.0'
> 
>   The above command will mean that paths in the tar archive look like:
>     project-1.0/project/src/main.c
>   etc.
> 
>   The second parameter allows you two strip the extraneous project, as in:
>     'git tar-tree --strippath=project --pathlimit=project project-1.0 tag-1.0     Which will result in tar archives looking like:
>     project-1.0/src/main.c
> 

This could be made more general and more Git-ish instead, by 
implementing a strip common prefix option and using a double dash option 
to signal that the remaining arguments are the paths of interest.

The synopsis would then look like:

	git-tar-tree [--remote=<repo>] [ --strip-common-prefix ]
		<tree-ish> [ <base> ] [ -- <paths>... ]

  reply	other threads:[~2006-07-30 18:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30 17:48 [PATCH 1/1] Make git-tar-tree more flexible Anand Kumria
2006-07-30 18:46 ` A Large Angry SCM [this message]
2006-07-30 20:57 ` Junio C Hamano
2006-07-31  0:26   ` Johannes Schindelin
2006-07-31  1:17     ` 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=44CCFE93.7040500@gmail.com \
    --to=gitzilla@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=wildfire@progsoc.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.