Re: documentation for committing with git
От | Andrew Dunstan |
---|---|
Тема | Re: documentation for committing with git |
Дата | |
Msg-id | 4C5A2A1F.2090804@dunslane.net обсуждение исходный текст |
Ответ на | Re: documentation for committing with git (Daniel Farina <drfarina@acm.org>) |
Список | pgsql-hackers |
On 08/04/2010 10:08 PM, Daniel Farina wrote: > On Wed, Aug 4, 2010 at 6:29 AM, Heikki Linnakangas > <heikki.linnakangas@enterprisedb.com> wrote: >> All those issues can be avoided if you only run "git gc" when all the >> working directories are in a clean state, with no staged but uncommitted >> changes or other funny things. I can live with that gun tied to my ankle >> ;-). > Does even that open a possibility for data loss? > > Use of the alternates feature will, to my knowledge, never write the > referenced repository: all new objects are held in the referencers. > The only condition as I understand it is not to generate garbage in > the reference repository, and that nominally does not happen in a repo > that exists only to be an object pool (you probably even want to use a > "bare" repository instead of one with checked out files). > > AIUI, git-new-workdir, which Heikki is proposing to use, does not work with bare clones. cheers andrew
В списке pgsql-hackers по дате отправления: