From: Pavel Roskin <proski@gnu.org>
To: Petr Baudis <pasky@suse.cz>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org, mj@ucw.cz
Subject: Re: Unresolved issues #2
Date: Thu, 04 May 2006 11:45:31 -0400 [thread overview]
Message-ID: <1146757531.5294.26.camel@dv> (raw)
In-Reply-To: <20060504095827.GW27689@pasky.or.cz>
Hello, Petr!
On Thu, 2006-05-04 at 11:58 +0200, Petr Baudis wrote:
> 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
next prev parent reply other threads:[~2006-05-04 15:46 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 9:31 Recent unresolved issues Junio C Hamano
2006-04-14 16:02 ` Petr Baudis
2006-04-14 19:10 ` sean
2006-04-14 19:10 ` sean
2006-04-14 19:24 ` Petr Baudis
2006-04-14 22:56 ` Recent unresolved issues: shallow clone Carl Worth
2006-04-15 0:17 ` Johannes Schindelin
2006-04-15 0:25 ` Junio C Hamano
2006-04-15 2:11 ` Junio C Hamano
2006-04-14 23:52 ` Recent unresolved issues Linus Torvalds
2006-04-15 0:19 ` Linus Torvalds
2006-04-15 0:39 ` Linus Torvalds
2006-04-15 0:38 ` Junio C Hamano
2006-04-15 0:49 ` Linus Torvalds
2006-04-15 0:56 ` Linus Torvalds
2006-04-15 1:09 ` Linus Torvalds
2006-04-15 2:22 ` Junio C Hamano
2006-04-15 6:18 ` Junio C Hamano
2006-04-15 8:57 ` Junio C Hamano
2006-04-15 11:46 ` Johannes Schindelin
2006-04-15 16:59 ` Linus Torvalds
2006-04-15 17:17 ` Linus Torvalds
2006-04-16 8:14 ` Junio C Hamano
2006-04-15 1:35 ` Junio C Hamano
2006-04-15 4:09 ` Linus Torvalds
2006-04-15 5:06 ` Junio C Hamano
2006-05-04 8:15 ` Unresolved issues #2 Junio C Hamano
2006-05-04 8:32 ` Jakub Narebski
2006-05-04 9:14 ` Junio C Hamano
2006-05-04 9:26 ` Jakub Narebski
2006-05-04 9:58 ` Petr Baudis
2006-05-04 15:45 ` Pavel Roskin [this message]
2006-05-04 17:01 ` Unresolved issues #2 (shallow clone again) Carl Worth
2006-05-05 0:25 ` Junio C Hamano
2006-05-05 5:17 ` Martin Langhoff
2006-05-05 5:23 ` Carl Worth
2006-05-05 5:48 ` Jakub Narebski
2006-05-05 15:10 ` Linus Torvalds
2006-05-05 15:18 ` Jakub Narebski
2006-05-05 15:59 ` Linus Torvalds
2006-05-06 6:23 ` Martin Langhoff
2006-05-06 7:10 ` Junio C Hamano
2006-05-07 6:08 ` Martin Langhoff
2006-05-07 7:56 ` Jeff King
2006-05-07 15:27 ` Linus Torvalds
2006-05-08 4:24 ` Jeff King
2006-05-08 15:32 ` Linus Torvalds
2006-05-08 0:33 ` Theodore Tso
2006-05-08 0:50 ` Linus Torvalds
2006-05-08 1:26 ` Theodore Tso
2006-05-08 2:04 ` Linus Torvalds
2006-05-08 2:24 ` Theodore Tso
2006-05-08 2:42 ` Linus Torvalds
2006-05-07 8:01 ` Sergey Vlasov
2006-05-07 23:27 ` Martin Langhoff
2006-05-07 23:35 ` Junio C Hamano
2006-05-07 23:44 ` Martin Langhoff
2006-05-05 15:31 ` Carl Worth
2006-05-07 13:30 ` Jakub Narebski
2006-05-08 2:54 ` Junio C Hamano
2006-05-08 4:02 ` Jakub Narebski
2006-05-08 4:24 ` Jakub Narebski
2006-05-04 20:41 ` Unresolved issues #2 Daniel Barkalow
2006-05-04 21:33 ` Linus Torvalds
2006-05-06 5:58 ` Junio C Hamano
2006-05-06 15:26 ` Linus Torvalds
2006-05-06 15:35 ` sean
2006-05-06 15:35 ` sean
2006-05-06 16:30 ` Linus Torvalds
2006-05-06 16:53 ` sean
2006-05-06 16:53 ` sean
2006-05-06 17:20 ` Linus Torvalds
2006-05-06 21:16 ` Junio C Hamano
2006-05-06 21:33 ` Johannes Schindelin
2006-05-06 21:51 ` Linus Torvalds
2006-05-07 9:39 ` Junio C Hamano
2006-05-07 9:42 ` Junio C Hamano
2006-05-07 11:31 ` Johannes Schindelin
2006-05-07 11:38 ` Jakub Narebski
2006-05-08 2:51 ` Junio C Hamano
2006-05-07 0:41 ` Jakub Narebski
2006-05-09 11:40 ` David Woodhouse
2006-05-09 11:53 ` Bertrand Jacquin
2006-05-09 13:09 ` Nicolas Pitre
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=1146757531.5294.26.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=mj@ucw.cz \
--cc=pasky@suse.cz \
/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.