From: "Ping Yin" <pkufranky@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Miklos Vajna" <vmiklos@frugalware.org>,
"Junio C Hamano" <gitster@pobox.com>,
"Richard Purdie" <rpurdie@rpsys.net>,
git@vger.kernel.org
Subject: Re: Tracability in git commits
Date: Thu, 1 May 2008 13:09:45 +0800 [thread overview]
Message-ID: <46dff0320804302209o2af9d630s48564a9b68c24ec1@mail.gmail.com> (raw)
In-Reply-To: <20080501002827.GX29771@spearce.org>
On Thu, May 1, 2008 at 8:28 AM, Shawn O. Pearce <spearce@spearce.org> wrote:
> `git config core.logAllRefUpdates true` right after you make the
> repository solves that nicely. I actually have a script that I use
> to make a new bare central repo:
>
> #!/bin/sh
> git --git-dir="$1" init &&
> git --git-dir="$1" config core.logAllRefUpdates true ||
> exit
I wonder why not make it the default behaviour. If someone push the
wrong commit to the bare repository (for example, with 'git push -f'),
there is no easy way to recover without reflog.
So as a solution, i would rather put this config to ~/.gitconfig
--
Ping Yin
next prev parent reply other threads:[~2008-05-01 5:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 12:55 Tracability in git commits Richard Purdie
2008-04-29 16:08 ` Johannes Schindelin
2008-04-29 21:34 ` Junio C Hamano
2008-04-29 21:56 ` Richard Purdie
2008-04-30 2:51 ` Shawn O. Pearce
2008-04-30 17:33 ` Ping Yin
2008-04-30 19:46 ` Miklos Vajna
2008-05-01 0:28 ` Shawn O. Pearce
2008-05-01 5:09 ` Ping Yin [this message]
2008-04-30 10:06 ` Jakub Narebski
2008-04-30 10:32 ` Richard Purdie
2008-05-01 1:26 ` Martin Langhoff
2008-05-01 7:34 ` Martin Langhoff
2008-05-01 19:03 ` Junio C Hamano
2008-05-01 22:21 ` Martin Langhoff
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=46dff0320804302209o2af9d630s48564a9b68c24ec1@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rpurdie@rpsys.net \
--cc=spearce@spearce.org \
--cc=vmiklos@frugalware.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).