git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 3/3] Teach git-index-pack how to keep a pack file.
Date: Sun, 29 Oct 2006 11:49:17 +0100	[thread overview]
Message-ID: <ei210e$dfs$1@sea.gmane.org> (raw)
In-Reply-To: 20061029094159.GE3847@spearce.org

Shawn Pearce wrote:

> +--keep::
> +       Before moving the index into its final destination
> +       create an empty .keep file for the associated pack file.
> +       This option is usually necessary with --stdin to prevent a
> +       simultaneous gitlink:git-repack[1] process from deleting
> +       the newly constructed pack and index before refs can be
> +       updated to use objects contained in the pack.
> +
> +--keep='why'::
> +       Like --keep create a .keep file before moving the index into
> +       its final destination, but rather than creating an empty file
> +       place 'why' followed by an LF into the .keep file.  The 'why'
> +       message can later be searched for within all .keep files to
> +       locate any which have outlived their usefulness.

Wouldn't it be better to use 'git-index-pack', perhaps with source URL if
possible, as the default 'why'?
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git


  reply	other threads:[~2006-10-29 10:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29  9:41 [PATCH 3/3] Teach git-index-pack how to keep a pack file Shawn Pearce
2006-10-29 10:49 ` Jakub Narebski [this message]
2006-10-29 19:14   ` Junio C Hamano
2006-10-29 19:44     ` Michael S. Tsirkin
2006-10-30  3:47 ` Nicolas Pitre

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='ei210e$dfs$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.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).