From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Do not ignore hidden refs
Date: Sun, 19 Nov 2006 00:18:42 +0100 [thread overview]
Message-ID: <20061118231842.GS7201@pasky.or.cz> (raw)
In-Reply-To: <7vy7q8bjwn.fsf@assigned-by-dhcp.cox.net>
On Sat, Nov 18, 2006 at 09:05:12PM CET, Junio C Hamano wrote:
> use heads/private/ for your own stuff. And have
> configuration that says "heads/private/" are private
> branches that are not subject to default
> pushing/pulling.
>
> The real instruction from the project would say what the syntax
> for telling that to git but I think you got the idea...
Yes, I fully agree that being able to have this configurable is cool,
but I'm still interested in providing a sensible out-of-the-box default
configuration for Cogito to use. But if we can agree that heads/private/
and tags/private/ are good BCP candidates, that's great. (The only
possible problem is a lot of typing incurred. Perhaps the default refs
search order should become configurable first.)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
The meaning of Stonehenge in Traflamadorian, when viewed from above, is:
"Replacement part being rushed with all possible speed."
next prev parent reply other threads:[~2006-11-18 23:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 4:11 [PATCH] Do not ignore hidden refs Petr Baudis
2006-11-18 4:39 ` Junio C Hamano
2006-11-18 4:53 ` Petr Baudis
2006-11-18 7:27 ` Junio C Hamano
2006-11-18 7:41 ` Shawn Pearce
2006-11-18 19:28 ` Petr Baudis
2006-11-18 19:50 ` Junio C Hamano
2006-11-18 19:55 ` Petr Baudis
2006-11-18 20:05 ` Junio C Hamano
2006-11-18 23:18 ` Petr Baudis [this message]
2006-11-19 0:29 ` Junio C Hamano
2006-11-19 0:48 ` Petr Baudis
2006-11-18 17:35 ` Linus Torvalds
2006-11-18 18:35 ` Junio C Hamano
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=20061118231842.GS7201@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.