* Re: git repository for net drivers available
[not found] ` <4284C7DA.1020707@pobox.com>
@ 2005-05-15 20:05 ` Petr Baudis
2005-05-15 20:20 ` Jeff Garzik
2005-05-15 21:46 ` Junio C Hamano
0 siblings, 2 replies; 3+ messages in thread
From: Petr Baudis @ 2005-05-15 20:05 UTC (permalink / raw)
To: Jeff Garzik; +Cc: James Ketrenos, Netdev, Linux Kernel, git
Dear diary, on Fri, May 13, 2005 at 05:29:30PM CEST, I got a letter
where Jeff Garzik <jgarzik@pobox.com> told me that...
> Looks like cogito is using $repo/heads/$branch, whereas my git repo is
> using $repo/branches/$branch.
Would it be a big problem to use refs/heads/$branch? That's the
currently commonly agreed convention about location for storing branch
heads, not just some weird Cogito-specific invention. And it'd be very
nice to have those locations consistent across git repositories.
Thanks,
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: git repository for net drivers available
2005-05-15 20:05 ` git repository for net drivers available Petr Baudis
@ 2005-05-15 20:20 ` Jeff Garzik
2005-05-15 21:46 ` Junio C Hamano
1 sibling, 0 replies; 3+ messages in thread
From: Jeff Garzik @ 2005-05-15 20:20 UTC (permalink / raw)
To: Petr Baudis; +Cc: James Ketrenos, Netdev, Linux Kernel, git, Andrew Morton
Petr Baudis wrote:
> Dear diary, on Fri, May 13, 2005 at 05:29:30PM CEST, I got a letter
> where Jeff Garzik <jgarzik@pobox.com> told me that...
>
>>Looks like cogito is using $repo/heads/$branch, whereas my git repo is
>>using $repo/branches/$branch.
>
>
> Would it be a big problem to use refs/heads/$branch? That's the
> currently commonly agreed convention about location for storing branch
> heads, not just some weird Cogito-specific invention. And it'd be very
> nice to have those locations consistent across git repositories.
Sure, that's doable.
I've pushed out this change to kernel.org.
Jeff
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: git repository for net drivers available
2005-05-15 20:05 ` git repository for net drivers available Petr Baudis
2005-05-15 20:20 ` Jeff Garzik
@ 2005-05-15 21:46 ` Junio C Hamano
1 sibling, 0 replies; 3+ messages in thread
From: Junio C Hamano @ 2005-05-15 21:46 UTC (permalink / raw)
To: Petr Baudis; +Cc: Jeff Garzik, Linux Kernel, git
>>>>> "PB" == Petr Baudis <pasky@ucw.cz> writes:
PB> Dear diary, on Fri, May 13, 2005 at 05:29:30PM CEST, I got a letter
PB> where Jeff Garzik <jgarzik@pobox.com> told me that...
>> Looks like cogito is using $repo/heads/$branch, whereas my git repo is
>> using $repo/branches/$branch.
PB> Would it be a big problem to use refs/heads/$branch? That's the
PB> currently commonly agreed convention about location for storing branch
PB> heads, not just some weird Cogito-specific invention. And it'd be very
PB> nice to have those locations consistent across git repositories.
Since Jeff brought up $repo/branches/$branch, you may also want
to add that $repo/branches/$branch is used to record the URL of
the remote $branch (the information used to be in a flat file
$repo/remotes, branch name and URL separated by shell $IFS, one
record on each line), and is quite different from those 40-byte
SHA1 plus LF files you see in $repo/refs/*/ directory.
I think it is a reasonable one, I also follow the
$repo/branches/$branch convention Cogito uses, and I would
encorage other Porcelain implementations to follow suit.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-05-15 21:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <42841A3F.7020909@pobox.com>
[not found] ` <4284C54E.3060907@linux.intel.com>
[not found] ` <4284C7DA.1020707@pobox.com>
2005-05-15 20:05 ` git repository for net drivers available Petr Baudis
2005-05-15 20:20 ` Jeff Garzik
2005-05-15 21:46 ` Junio C Hamano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).