From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: "Cristian Le" <cristian.le@mpsd.mpg.de>,
git@vger.kernel.org,
"Matthias Görgens" <matthias.goergens@gmail.com>
Subject: Re: Bug in git archive + .gitattributes + relative path
Date: Mon, 20 Mar 2023 09:16:37 -0700 [thread overview]
Message-ID: <xmqqlejro0t6.fsf@gitster.g> (raw)
In-Reply-To: <9e215e5c-0b67-0362-fd53-8c22b8d348ff@web.de> ("René Scharfe"'s message of "Sat, 18 Mar 2023 22:30:24 +0100")
René Scharfe <l.s.r@web.de> writes:
>> $ cd some/deep/place
>> ... work work work
>> $ git archive --full-tree :/other :/hier :/archy
>>
>> is what I had in mind. Without --full-tree, due to the first bullet
>> point above, paths in our archive are relative to some/deep/place.
>
> I don't see the difference.
OK. I do not work in Java anyway ;-)
next prev parent reply other threads:[~2023-03-20 16:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 10:25 Bug in git archive + .gitattributes + relative path Cristian Le
2023-03-03 15:19 ` René Scharfe
2023-03-03 15:38 ` Cristian Le
2023-03-04 13:58 ` René Scharfe
2023-03-04 15:11 ` Cristian Le
2023-03-05 9:32 ` René Scharfe
2023-03-06 16:56 ` Junio C Hamano
2023-03-06 17:51 ` René Scharfe
2023-03-06 17:27 ` Junio C Hamano
2023-03-06 18:28 ` René Scharfe
2023-03-06 18:59 ` Junio C Hamano
2023-03-06 21:32 ` René Scharfe
2023-03-06 22:34 ` Junio C Hamano
2023-03-11 20:47 ` René Scharfe
2023-03-12 21:25 ` Junio C Hamano
2023-03-18 21:30 ` René Scharfe
2023-03-20 16:16 ` Junio C Hamano [this message]
2023-03-20 20:02 ` [PATCH] archive: improve support for running in a subdirectory René Scharfe
2023-03-21 22:59 ` Junio C Hamano
2023-03-24 22:26 ` René Scharfe
2023-03-24 22:27 ` [PATCH v2] archive: improve support for running in subdirectory René Scharfe
2023-03-27 16:09 ` 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=xmqqlejro0t6.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=cristian.le@mpsd.mpg.de \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=matthias.goergens@gmail.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.
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.