Re: ghost refs
- From
Jeff King <peff@peff.net>
- Date
- Apr 8, 2010, 19:49 UTC
- Message-ID
- <20100408194908.GB4222@sigill.intra.peff.net>
- In-Reply-To
- <7vwrwh6fz8.fsf@alter.siamese.dyndns.org>
On Thu, Apr 08, 2010 at 09:55:55AM -0700, Junio C Hamano wrote:
Show 12 quoted lines
> John Dlugosz <JDlugosz@TradeStation.com> writes:
>
> > In git-branch,
> >
> > -l
> >
> > Create the branch's reflog. This activates recording of all
> > changes made to the branch ref, enabling use of date based
> > sha1 expressions such as "<branchname>@{yesterday}".
>
> That is how you selectively enable reflog for that particular branch when
> you have explicitly disabled "reflog by default" with the configuration.Maybe:
-- >8 -- Subject: [PATCH] docs: clarify "branch -l"
This option is mostly useless these days because we turn on reflogs by default in non-bare repos.
Signed-off-by: Jeff King <peff@peff.net> --- Documentation/git-branch.txt | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt index 903a690..d78f4c7 100644 --- a/Documentation/git-branch.txt +++ b/Documentation/git-branch.txt @@ -72,6 +72,8 @@ OPTIONS Create the branch's reflog. This activates recording of all changes made to the branch ref, enabling use of date based sha1 expressions such as "<branchname>@\{yesterday}". + Note that in non-bare repositories, reflogs are usually + enabled by default by the `core.logallrefupdates` config option. -f:: --force::
-- 1.7.1.rc0.248.g055378.dirty