Re: [PATCH 08/11] Allow for having for_each_ref() list some refs that aren't local

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Daniel Barkalow <barkalow@xxxxxxxxxxxx> writes:

> This is useful, for example, for listing the refs in a reference
> repository during clone, when you don't have your own refs that cover
> the objects that are in your alternate repository.

I hate to ask a question that I myself do not have a good answer to, but
it is a bit worrysome that using these extra refs would cause for-each-ref
to report different refs with the same name (the alternate's master branch
and this one's master branch are both called refs/heads/master).

I think no caller that reads from for_each_ref() keeps track of names that
it has seen and tries clever things like flagging duplicates as errors,
but it still feels like it is inviting trouble.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux