From: Jeff King <peff@peff.net>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: "Brandon Casey" <drafnel@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Ævar Arnfjörð" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git auto-repack is broken...
Date: Wed, 7 Dec 2011 22:40:38 -0500 [thread overview]
Message-ID: <20111208034038.GA2280@sigill.intra.peff.net> (raw)
In-Reply-To: <alpine.LFD.2.02.1112072227510.2907@xanadu.home>
On Wed, Dec 07, 2011 at 10:35:00PM -0500, Nicolas Pitre wrote:
> And I don't think this particular case is interesting anyway as the
> reflogs for the various branches alre already involved. I was thinking
> more about the "git fetch git://some.random.repo foobar" case where the
> summary also explicitly shows:
>
> From: git://some.random.repo
> ...... foobar -> FETCH_HEAD
>
> In that case the only reference to the fetched branch is stored in
> FETCH_HEAD and that is what might be worthwile for a reflog.
I agree that is the interesting case. Perhaps we could just not bother
writing the other case into the reflog at all. So the reflog would be
sensible and contain only the set of things they had fetched or pulled
explicitly by URL. If they really want to do a multi-ref one-off fetch
from some URL, then we write multiple reflog entries. But at least the
user is very aware of what they've done, so they're not surprised by the
reflog advancing by more than 1 entry.
-Peff
next prev parent reply other threads:[~2011-12-08 3:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 16:22 git auto-repack is broken Linus Torvalds
2011-12-02 16:27 ` Ævar Arnfjörð Bjarmason
2011-12-02 16:56 ` Linus Torvalds
2011-12-02 17:10 ` Jeff King
2011-12-02 17:35 ` Junio C Hamano
2011-12-02 17:45 ` Jeff King
2011-12-02 18:08 ` Junio C Hamano
2011-12-02 18:13 ` Jeff King
2011-12-03 19:42 ` Brandon Casey
2011-12-07 22:12 ` Nicolas Pitre
2011-12-07 22:53 ` Jeff King
2011-12-08 0:18 ` Nicolas Pitre
2011-12-08 0:45 ` Jeff King
2011-12-08 3:35 ` Nicolas Pitre
2011-12-08 3:40 ` Jeff King [this message]
2011-12-09 17:35 ` Junio C Hamano
2011-12-09 18:34 ` Nicolas Pitre
2011-12-08 0:49 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2011-12-03 6:55 George Spelvin
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=20111208034038.GA2280@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@fluxnic.net \
--cc=torvalds@linux-foundation.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).