From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Marking abandoned branches
Date: Wed, 13 Sep 2006 23:32:24 +0200 [thread overview]
Message-ID: <ee9tcl$h98$2@sea.gmane.org> (raw)
In-Reply-To: 7vhczb7ay9.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> What this suggests is that the core support we
> will give needs a way to specify what subset of refs/* to
> include. peek-remote allows you to do this and it is fairly
> efficient for local case (although it could be made more
> efficient by not using the general git_connect() framework if we
> want a faster local-only command), but it gives back only the
> object names.
What is the difference between peek-remote and ls-remotes in the
local case, by the way?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-13 21:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 15:17 Marking abandoned branches Jon Smirl
2006-09-13 15:24 ` Petr Baudis
2006-09-13 15:31 ` Johannes Schindelin
2006-09-13 15:45 ` Jakub Narebski
2006-09-13 18:40 ` Junio C Hamano
2006-09-13 18:51 ` Jakub Narebski
2006-09-13 19:00 ` Junio C Hamano
2006-09-13 19:34 ` Jakub Narebski
2006-09-13 20:43 ` Petr Baudis
2006-09-13 20:45 ` Junio C Hamano
2006-09-13 21:02 ` Jakub Narebski
2006-09-13 21:09 ` Jakub Narebski
2006-09-13 21:32 ` Jakub Narebski [this message]
2006-09-13 15:59 ` Jon Smirl
2006-09-13 16:05 ` Johannes Schindelin
2006-09-13 17:22 ` Jon Smirl
2006-09-13 17:32 ` Shawn Pearce
2006-09-13 17:46 ` Nicolas Pitre
2006-09-13 20:31 ` Martin Langhoff
2006-09-13 20:43 ` Jakub Narebski
2006-09-13 16:09 ` Shawn Pearce
2006-09-13 16:12 ` Jakub Narebski
2006-09-13 16:40 ` A Large Angry SCM
2006-09-13 16:49 ` Shawn Pearce
2006-09-13 18:58 ` Junio C Hamano
2006-09-13 16:55 ` Jakub Narebski
2006-09-13 17:24 ` Jon Smirl
2006-09-13 17:45 ` Jakub Narebski
2006-09-14 3:37 ` Sam Vilain
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='ee9tcl$h98$2@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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 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).