From: Jay Soffian <jaysoffian@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Shawn Pearce <spearce@spearce.org>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Nicolas Pitre <nico@fluxnic.net>,
John Hawley <warthog19@eaglescrag.net>
Subject: Re: [RFC] Add --create-cache to repack
Date: Fri, 28 Jan 2011 14:15:30 -0500 [thread overview]
Message-ID: <AANLkTi=f34Q2VUrzA0dEG0KCFcHcd_Yq=UN6RSDPVS+p@mail.gmail.com> (raw)
In-Reply-To: <4D42E1E3.4060808@viscovery.net>
On Fri, Jan 28, 2011 at 10:33 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Let's define a ref hierarchy, refs/cache-pack, that names the cache pack
> tips. A cache pack would be generated for each ref found in that
> hierarchy. Then these commits are under user control even on github,
> because you can just push the refs. Junio would perhaps choose a release
> tag, and corresponding commits in the man and html histories. The choice
> would not be completely automatic, though.
This is just for bare repos, right? Why not just use HEAD?
j.
next prev parent reply other threads:[~2011-01-28 19:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 8:06 [RFC] Add --create-cache to repack Shawn O. Pearce
2011-01-28 9:08 ` Johannes Sixt
2011-01-28 14:37 ` Shawn Pearce
2011-01-28 15:33 ` Johannes Sixt
2011-01-28 18:22 ` Shawn Pearce
2011-01-28 19:15 ` Jay Soffian [this message]
2011-01-28 19:19 ` Shawn Pearce
2011-01-28 18:46 ` Nicolas Pitre
2011-01-28 19:15 ` Shawn Pearce
2011-01-28 21:09 ` Nicolas Pitre
2011-01-29 1:32 ` Shawn Pearce
2011-01-29 2:34 ` Shawn Pearce
2011-01-30 8:05 ` Junio C Hamano
2011-01-30 19:43 ` Shawn Pearce
2011-01-30 20:02 ` Junio C Hamano
2011-01-30 20:20 ` Shawn Pearce
2011-01-30 22:26 ` Nicolas Pitre
2011-01-29 4:08 ` Nicolas Pitre
2011-01-29 4:35 ` Shawn Pearce
2011-01-30 6:51 ` Junio C Hamano
2011-01-30 17:14 ` Nicolas Pitre
2011-01-30 17:41 ` A Large Angry SCM
2011-01-30 19:29 ` Shawn Pearce
2011-01-30 22:13 ` Shawn Pearce
2011-01-31 18:47 ` Shawn Pearce
2011-01-31 21:48 ` 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='AANLkTi=f34Q2VUrzA0dEG0KCFcHcd_Yq=UN6RSDPVS+p@mail.gmail.com' \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=nico@fluxnic.net \
--cc=spearce@spearce.org \
--cc=warthog19@eaglescrag.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 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).