Re: Unresolved issues #2
- From
- Pavel Roskin <proski@gnu.org>
- Date
- May 4, 2006, 15:45 UTC
- Message-ID
- <1146757531.5294.26.camel@dv>
- In-Reply-To
- <20060504095827.GW27689@pasky.or.cz>
Hello, Petr!
On Thu, 2006-05-04 at 11:58 +0200, Petr Baudis wrote:
Show 9 quoted lines
> Oh, my holey memory. In Cogito, I have just implemented a solution > suggested by Martin Mares, which is pretty simple, non-obtrusive > and will work equally fine with remotes as well as remote branches: > > if [ $branch != master ] && [ -s .git/branches/$branch-origin ] > origin=.git/branches/$branch-origin > else > origin=.git/branches/origin > fi
Isn't ".git/branches" obsolete, at least in git? I'm surprised it's still referenced in git sources.
What is the future of ".git/branches"? Is it becoming a Cogito specific branch database? Or is it now a database or branch dependencies?
I would prefer to have one single standard for branch origins that could be used by git, StGIT and Cogito. Using a location that is obsolete outside Cogito is probably the worst possible approach. I'd rather have a separate directory, e.g. .git/origins or something.
Alternatively, we could reuse .git/refs by having files with "Pull:" but without "URI:", e.g.
$ cat .git/refs/branch Pull: branch-origin:branch
-- Regards, Pavel Roskin