All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: killing a branch
Date: Tue, 10 Jan 2006 19:59:32 +0100	[thread overview]
Message-ID: <20060110185932.GW3389@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0601100910530.4939@g5.osdl.org>

On Tue, Jan 10 2006, Linus Torvalds wrote:
> 
> 
> On Tue, 10 Jan 2006, Jens Axboe wrote:
> > 
> > Alright, I'll just have to shake the habit of running git prune to rid
> > myself of that dirty dirty feeling.
> 
> Yeah, I'm slowly shaking it off too. I used to run git-fsck-objects 
> religiously just because I worried about bugs. I still do it, but 
> especially with the recursive-strategy merging, I get "dangling blob" 
> messages every once in a while that are _not_ due to bugs, but just due to 
> the temporary merge object.
> 
> So I'm learning to ignore them, and prune the tree only occasionally, 
> instead of compulsively every time.

Compulsive is the right word, it just itches to run the prune after
killing a branch... I'll try and learn as well.

-- 
Jens Axboe

  reply	other threads:[~2006-01-10 18:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10 10:22 killing a branch Jens Axboe
2006-01-10 10:25 ` Junio C Hamano
2006-01-10 10:35   ` Jens Axboe
2006-01-10 10:52     ` Junio C Hamano
2006-01-10 11:26       ` Jens Axboe
2006-01-10 17:12         ` Linus Torvalds
2006-01-10 18:59           ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-12  9:57 linux

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=20060110185932.GW3389@suse.de \
    --to=axboe@suse.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.