Hi,
On Mon, 2 Jun 2008, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes:
>
> > After sending the mail, I actually got an idea:
> >
> > .git/logs/attic/<timestamp>/<refname>
> >
> > I think this should work without problems. In that case, git-gc also
> > handles the garbage collection.
>
> I do not like that particular color of the bikeshed, but I'd agree that
> it certainly is the easiest route from both the implementation and the
> design point of view.
Okay, how about "deleted-%d.%m.%Y-%H:%M:%S" instead of "attic/%s"?
> All of the "hard stuff" Shawn mentions goes away, and you are left with
> only one new "hard stuff", which is much easier to solve:
>
> - Should there be a way to really remove the archived reflog?
>
> And my answer is "yes, a new subcommand to 'git-reflog' to list and
> another subcommand to remove one".
You mean a subcommand to list just the refs that exist in the deleted-*
namespace?
As to remove one, how about:
git reflog --expire=now --expire-unreachable=now \
deleted-<date>/<refname>
Hmm?
> As to default behaviour, probably we would by default archive any local
> branches, and _not_ archive other things like remote trackers and tags.
Unfortunately, this is exactly what I need: remote trackers and tags.
Since I have to delete branches from repo.or.cz as long as the pruning of
forked projects' objects does not work correctly.
> A new configuration variable reflog.archive = {none,heads,all} would be
> honored and absense of it defaults to reflog.archive = heads.
Sure, that makes sense. I'd just "git config --global reflog.archive
all".
Ciao,
Dscho
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
