From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] [BUG] Add a test to check git-prune does not throw away revs hidden by a graft.
Date: Fri, 19 May 2006 21:00:00 +0200 [thread overview]
Message-ID: <e4l4j1$vkq$1@sea.gmane.org> (raw)
In-Reply-To: 20060519185558.GE6535@nowhere.earth
Yann Dirson wrote:
> On Thu, May 18, 2006 at 03:53:36PM -0700, Junio C Hamano wrote:
>> Yann Dirson <ydirson@altern.org> writes:
>>
>> > To make my point maybe more clear: if someone really wants to make a
>> > graft permanent, wouldn't some history rewriting ... be the
>> > way to go,...
>>
>> Yes.
>
> So if temporary usage is a typical use for grafts, don't we want to
> protect people using them from pruning ? I got no feedback to my
> suggestion of changing the default behaviour, even to say it was a bad
> idea :)
Perhaps prune should be conservative by default, and follow both grafts and
original parents, and use appropriate options to preserve or not preserve
grafts.
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-05-19 19:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 21:35 [PATCH] [BUG] Add a test to check git-prune does not throw away revs hidden by a graft Yann Dirson
2006-05-18 21:37 ` Linus Torvalds
2006-05-18 21:46 ` Junio C Hamano
2006-05-18 22:01 ` Linus Torvalds
2006-05-18 22:25 ` Junio C Hamano
2006-05-18 22:20 ` Yann Dirson
2006-05-18 22:36 ` Junio C Hamano
2006-05-18 22:52 ` Yann Dirson
2006-05-18 22:53 ` Junio C Hamano
2006-05-19 18:55 ` Yann Dirson
2006-05-19 19:00 ` Jakub Narebski [this message]
2006-05-19 19:02 ` Linus Torvalds
2006-05-19 20:25 ` Yann Dirson
2006-05-19 20:45 ` Linus Torvalds
2006-05-19 22:22 ` Junio C Hamano
2006-05-19 22:26 ` [PATCH] [BUG] Add a test to check git-prune does not throw awayrevs " David Lang
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='e4l4j1$vkq$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 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.