Re: [PATCH v6 3/3] bundle doc: elaborate on rev<->ref restriction

2 messages, 2 authors, 2021-07-21 · open the first message on its own page

Re: [PATCH v6 3/3] bundle doc: elaborate on rev<->ref restriction

From: Junio C Hamano <hidden>
Date: 2021-07-20 20:43:12

Ævar Arnfjörð Bjarmason  [off-list ref] writes:
+Revisions must accompanied by reference names to be packaged in a
+bundle, since the header of the bundle is in a format similar to 'git
+show-ref'.
This may be an improvement in the way how the description refers to
"show-ref", but we do not have to say anything about "show-ref" ;-)

The reason we should give readers why they must give refs while
creating a bundle, I think, is because the only way to access the
contents of the bundle is to fetch refs from it, and the refs given
to the command when the bundle was created becomes the refs that can
be fetched from the bundle.

Thanks.

Re: [PATCH v6 3/3] bundle doc: elaborate on rev<->ref restriction

From: Philip Oakley <hidden>
Date: 2021-07-21 09:35:28

On 20/07/2021 21:19, Junio C Hamano wrote:
Ævar Arnfjörð Bjarmason  [off-list ref] writes:
quoted
+Revisions must accompanied by reference names to be packaged in a
+bundle, since the header of the bundle is in a format similar to 'git
+show-ref'.
This may be an improvement in the way how the description refers to
"show-ref", but we do not have to say anything about "show-ref" ;-)

The reason we should give readers why they must give refs while
creating a bundle, I think, is because the only way to access the
contents of the bundle is to fetch refs from it, and the refs given
to the command when the bundle was created becomes the refs that can
be fetched from the bundle.

Thanks.
Should the `list-heads` option be mentioned for investigating existing
bundles?
--
Philip
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help