All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl Baldwin <cnb@fc.hp.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [Question] info/grafts file.
Date: Mon, 14 Nov 2005 17:03:49 -0700	[thread overview]
Message-ID: <20051115000349.GA32136@hpsvcnb.fc.hp.com> (raw)
In-Reply-To: <7vhdafx81m.fsf@assigned-by-dhcp.cox.net>

This is fine, I just needed to know.

How hard is it to, in a generic way, take a grafts file and reconstruct
commits to include the parents in the graft file in the actual tree?  I
am wondering because I couldn't, after much work, get git-svnimport to
find my merges correctly.  So, I am needing to hand-graft some merges in
to make things right.  Any suggestions?  I could try to figure something
out if I can find some time.  I'm good with graph traversals and such.

Carl

On Mon, Nov 14, 2005 at 12:56:37PM -0800, Junio C Hamano wrote:
> Grafts are considered local preference, and not copied when
> cloned.  I am unsure this was a right decision, but that is how
> things are right now.
> 

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 Carl Baldwin                        Systems VLSI Laboratory
 Hewlett Packard Company
 MS 88                               work: 970 898-1523
 3404 E. Harmony Rd.                 work: Carl.N.Baldwin@hp.com
 Fort Collins, CO 80525              home: Carl@ecBaldwin.net
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  reply	other threads:[~2005-11-15  0:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 18:20 [Question] info/grafts file Carl Baldwin
2005-11-14 19:59 ` Petr Baudis
2005-11-14 20:56 ` Junio C Hamano
2005-11-15  0:03   ` Carl Baldwin [this message]
2005-11-15  8:31     ` Alan Chandler
2005-11-15 17:16       ` Linus Torvalds
2005-11-17  0:57     ` Ryan Anderson
2005-11-17 21:45       ` Yann Dirson

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=20051115000349.GA32136@hpsvcnb.fc.hp.com \
    --to=cnb@fc.hp.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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.